1. 25 Mar, 2019 1 commit
  2. 13 Mar, 2019 1 commit
  3. 07 Mar, 2019 2 commits
  4. 06 Mar, 2019 1 commit
    • Patrick Bajao's avatar
      Accept force option on commit via API · de5aef3b
      Patrick Bajao authored
      When `force` is set to `true` and `start_branch` is set, the
      branch will be ovewritten with the new commit based on the
      `HEAD` of the `start_branch`.
      
      This commit includes changes to update the `gitaly-proto` gem.
      de5aef3b
  5. 02 Mar, 2019 1 commit
    • John Cai's avatar
      Removing old code path for search_files_by_content · 87adc799
      John Cai authored
      In 11.8, we added a fix for the SearchFilesByContent RPC in gitaly to
      send back the response in chunks. However, we kept in the old code path
      for backwards compatibility. Now that the change is fully deployed, we
      can remove that old codepath.
      87adc799
  6. 25 Feb, 2019 1 commit
    • Oswaldo Ferreira's avatar
      Support merge to ref for merge-commit and squash · 1ad69967
      Oswaldo Ferreira authored
      Adds the ground work for writing into
      the merge ref refs/merge-requests/:iid/merge the
      merge result between source and target branches of
      a MR, without further side-effects such as
      mailing, MR updates and target branch changes.
      1ad69967
  7. 15 Feb, 2019 1 commit
  8. 13 Feb, 2019 1 commit
  9. 11 Feb, 2019 1 commit
  10. 07 Feb, 2019 2 commits
  11. 06 Feb, 2019 1 commit
  12. 05 Feb, 2019 1 commit
    • Nick Thomas's avatar
      Fix a conflict in GITALY_SERVER_VERSION · d18cd4ad
      Nick Thomas authored
      GitLab.com master now points at Gitaly v1.17.0. Dev master pointed at
      1.14.1 due to a recent security release. That fix is present in 1.17.0
      so it is safe to take the .com side here.
      d18cd4ad
  13. 01 Feb, 2019 1 commit
  14. 31 Jan, 2019 1 commit
  15. 24 Jan, 2019 1 commit
  16. 22 Jan, 2019 1 commit
  17. 16 Jan, 2019 1 commit
  18. 22 Dec, 2018 1 commit
  19. 19 Dec, 2018 1 commit
  20. 17 Dec, 2018 1 commit
  21. 06 Dec, 2018 1 commit
  22. 27 Nov, 2018 1 commit
  23. 26 Nov, 2018 1 commit
  24. 23 Nov, 2018 1 commit
  25. 19 Nov, 2018 1 commit
  26. 14 Nov, 2018 1 commit
  27. 07 Nov, 2018 1 commit
  28. 05 Nov, 2018 1 commit
  29. 23 Oct, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Bump Gitaly to v0.126.0 · c40b5aaa
      Zeger-Jan van de Weg authored
      This will allow changes in Gitaly that will make it fail when running
      rspec, to make it to GitLab.
      
      Else Gitaly won't start as it can't reach the broken storage directory.
      c40b5aaa
  30. 15 Oct, 2018 1 commit
  31. 06 Oct, 2018 1 commit
  32. 04 Oct, 2018 1 commit
  33. 01 Oct, 2018 1 commit
  34. 27 Sep, 2018 1 commit
  35. 13 Sep, 2018 1 commit
  36. 07 Sep, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Port cleanup tasks to use Gitaly · 3aedccb1
      Zeger-Jan van de Weg authored
      Rake tasks cleaning up the Git storage were still using direct disk
      access, which won't work if these aren't attached. To mitigate a
      migration issue was created.
      
      To port gitlab:cleanup:dirs, and gitlab:cleanup:repos, a new RPC was
      required, ListDirectories. This was implemented in Gitaly, through
      https://gitlab.com/gitlab-org/gitaly/merge_requests/868.
      
      To be able to use the new RPC the Gitaly server was bumped to v0.120.
      
      This is an RPC that will not use feature gates, as this doesn't scale on
      .com so there is no way to test it at scale. Futhermore, we _know_ it
      doesn't scale, but this might be a useful task for smaller instances.
      
      Lastly, the tests are slightly updated to also work when the disk isn't
      attached. Eventhough this is not planned, it was very little effort and
      thus I applied the boy scout rule.
      
      Closes https://gitlab.com/gitlab-org/gitaly/issues/954
      Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40529
      3aedccb1
  37. 06 Sep, 2018 1 commit
  38. 17 Aug, 2018 1 commit