Read about our upcoming Code of Conduct on this issue

  1. 06 Jul, 2017 1 commit
    • Yorick Peterse's avatar
      Add many foreign keys to the projects table · 8b8987deee58
      Yorick Peterse authored
      This removes the need for relying on Rails' "dependent" option for data
      removal, which is _incredibly_ slow (even when using :delete_all) when
      deleting large amounts of data. This also ensures data consistency is
      enforced on DB level and not on application level (something Rails is
      really bad at).
      
      This commit also includes various migrations to add foreign keys to
      tables that eventually point to "projects" to ensure no rows get
      orphaned upon removing a project.
      8b8987deee58
  2. 05 Jul, 2017 1 commit
  3. 04 Jul, 2017 1 commit
  4. 26 Jun, 2017 1 commit
  5. 23 Jun, 2017 1 commit
  6. 22 Jun, 2017 1 commit
  7. 21 Jun, 2017 3 commits
  8. 16 Jun, 2017 2 commits
    • Sean McGivern's avatar
      Add table for files in merge request diffs · 5e72ebc31d73
      Sean McGivern authored
      This adds an ID-less table containing one row per file, per merge request
      diff. It has a column for each attribute on Gitlab::Git::Diff that is serialised
      currently, with the advantage that we can easily query the attributes of this
      new table.
      
      It does not migrate existing data, so we have fallback code when the legacy
      st_diffs column is present instead. For a merge request diff to be valid, it
      should have at most one of:
      
      * Rows in this new table, with the correct merge_request_diff_id.
      * A non-NULL st_diffs column.
      
      It may have neither, if the diff is empty.
      5e72ebc31d73
    • Felipe Artur's avatar
      9d91d1150c68
  9. 15 Jun, 2017 2 commits
    • Sean McGivern's avatar
      Deserialise existing custom notification settings · eed4b94a8185
      Sean McGivern authored
      Create a post-deployment migration to update all existing notification settings
      with at least one custom level enabled to the new format. Also handle the same
      conversion when updating settings, to catch any stragglers.
      eed4b94a8185
    • Sean McGivern's avatar
      Add columns for custom notification settings · b2803106e4cb
      Sean McGivern authored
      Add columns for each custom notification level, defaulting to null. Read from
      those columns if non-null, otherwise fall back to the serialized column. Writing
      will write to the new column if `events` isn't manually set.
      b2803106e4cb
  10. 14 Jun, 2017 1 commit
  11. 08 Jun, 2017 2 commits
    • DJ Mountney's avatar
      Bring in security changes from the 9.2.5 release · a5d6048d960f
      DJ Mountney authored
      Ran:
       - git format-patch v9.2.2..v9.2.5 --stdout > patchfile.patch
       - git checkout -b 9-2-5-security-patch origin/v9.2.2
       - git apply patchfile.patch
       - git commit
       - [Got the sha ref for the commit]
       - git checkout -b upstream-9-2-security master
       - git cherry-pick <SHA of the patchfile commit>
       - [Resolved conflicts]
       - git cherry-pick --continue
      a5d6048d960f
    • DJ Mountney's avatar
      Bring in security changes from the 9.2.5 release · 67d8f2be7b6e
      DJ Mountney authored
      Ran:
       - git format-patch v9.2.2..v9.2.5 --stdout > patchfile.patch
       - git checkout -b 9-2-5-security-patch origin/v9.2.2
       - git apply patchfile.patch
       - git commit
       - [Got the sha ref for the commit]
       - git checkout -b upstream-9-2-security master
       - git cherry-pick <SHA of the patchfile commit>
       - [Resolved conflicts]
       - git cherry-pick --continue
      67d8f2be7b6e
  12. 07 Jun, 2017 1 commit
  13. 06 Jun, 2017 1 commit
  14. 05 Jun, 2017 1 commit
  15. 02 Jun, 2017 2 commits
  16. 01 Jun, 2017 3 commits
  17. 31 May, 2017 4 commits
  18. 26 May, 2017 4 commits
  19. 25 May, 2017 2 commits
  20. 24 May, 2017 3 commits
  21. 23 May, 2017 1 commit
  22. 19 May, 2017 2 commits