Read about our upcoming Code of Conduct on this issue

  1. 07 Jan, 2019 1 commit
  2. 04 Jan, 2019 1 commit
  3. 13 Dec, 2018 1 commit
    • Alessio Caiazza's avatar
      Add name, author and sha to releases · 1d2319685e1a
      Alessio Caiazza authored
      This commit adds a name to each release, defaulting it to tag name,
      keeps track of the SHA when a new release is created and tracks the
      current user as release author.
      1d2319685e1a
  4. 05 Dec, 2018 1 commit
  5. 05 Oct, 2018 1 commit
  6. 02 Oct, 2018 1 commit
  7. 07 Sep, 2018 1 commit
  8. 04 Sep, 2018 1 commit
  9. 13 Aug, 2018 1 commit
    • Duana Saskia's avatar
      Filter project hooks by branch · 11a03100ca1c
      Duana Saskia authored
      Allow specificying a branch filter for a project hook and only trigger
      a project hook if either the branch filter is blank or the branch matches.
      Only supported for push_events for now.
      11a03100ca1c
  10. 08 Jun, 2018 1 commit
  11. 02 Jun, 2018 1 commit
  12. 01 Jun, 2018 1 commit
  13. 30 May, 2018 1 commit
  14. 29 May, 2018 1 commit
  15. 11 May, 2018 1 commit
  16. 01 May, 2018 1 commit
  17. 24 Apr, 2018 2 commits
  18. 20 Apr, 2018 1 commit
  19. 16 Apr, 2018 1 commit
    • Yorick Peterse's avatar
      Introduce new ProjectCiCdSetting · 748b19fa2048
      Yorick Peterse authored
      This model and the corresponding table will be used for storing settings
      specific to CI/CD, starting with the "group_runners_enabled" boolean.
      
      The model is called ProjectCiCdSetting and not ProjectCiCdSettings. The
      project exporter doesn't like plural model names as it uses "classify"
      which turns those into singular (so "ProjectCiCdSettings" becomes
      "ProjectCiCdSetting", producing an error if said class is undefined).
      
      The initial work in this commit was done by Dylan Griffith, with most of
      the migration work being done by Yorick Peterse.
      748b19fa2048
  20. 05 Apr, 2018 1 commit
  21. 28 Mar, 2018 2 commits
  22. 22 Mar, 2018 1 commit
  23. 07 Mar, 2018 1 commit
  24. 05 Mar, 2018 1 commit
  25. 01 Mar, 2018 1 commit
  26. 28 Feb, 2018 2 commits
  27. 07 Feb, 2018 1 commit
  28. 10 Jan, 2018 1 commit
    • Jan Provaznik's avatar
      Denormalize commits count for merge request diffs · fc52079e6da2
      Jan Provaznik authored
      For each MR diff an extra 'SELECT COUNT()' is executed
      to get number of commits for the diff. Overall time to get counts for
      all MR diffs may be quite expensive. To speed up loading of MR info,
      information about number of commits is stored in a MR diff's extra column.
      
      Closes #38068
      fc52079e6da2
  29. 08 Jan, 2018 1 commit
  30. 05 Jan, 2018 1 commit
  31. 24 Dec, 2017 1 commit
  32. 28 Nov, 2017 1 commit
    • Sean McGivern's avatar
      Remove serialised diff and commit columns · 701b9ccc8a4b
      Sean McGivern authored
      The st_commits and st_diffs columns on merge_request_diffs historically held the
      YAML-serialised data for a merge request diff, in a variety of formats.
      
      Since 9.5, these have been migrated in the background to two new tables:
      merge_request_diff_commits and merge_request_diff_files. That has the advantage
      that we can actually query the data (for instance, to find out how many commits
      we've stored), and that it can't be in a variety of formats, but must match the
      new schema.
      
      This is the final step of that journey, where we drop those columns and remove
      all references to them. This is a breaking change to the importer, because we
      can no longer import diffs created in the old format, and we cannot guarantee
      the export will be in the new format unless it was generated after this commit.
      701b9ccc8a4b
  33. 06 Nov, 2017 1 commit
  34. 02 Nov, 2017 1 commit
  35. 01 Nov, 2017 1 commit
  36. 31 Oct, 2017 1 commit
  37. 13 Oct, 2017 1 commit