An error occurred fetching the project authors.
  1. 02 May, 2018 1 commit
  2. 01 May, 2018 1 commit
  3. 03 Apr, 2018 1 commit
  4. 23 Mar, 2018 1 commit
  5. 21 Mar, 2018 1 commit
  6. 13 Mar, 2018 2 commits
  7. 12 Mar, 2018 3 commits
  8. 06 Mar, 2018 2 commits
  9. 15 Jan, 2018 1 commit
  10. 09 Jan, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Migrate GitlabProject (re)move project endpoints · 58e17bf3
      Zeger-Jan van de Weg authored
      Migration is done through a small refactoring, which makes us call
      endpoins which are performing the same actions for namespaces.
      Tests are added to ensure only the project is removed that should be
      removed.
      
      Closes gitlab-org/gitaly#873
      58e17bf3
  11. 02 Jan, 2018 1 commit
  12. 14 Dec, 2017 2 commits
    • Nick Thomas's avatar
      Import gitlab_projects.rb from gitlab-shell · 28a98db7
      Nick Thomas authored
      By importing this Ruby code into gitlab-rails (and gitaly-ruby), we avoid
      200ms of startup time for each gitlab_projects subprocess we are eliminating.
      
      By not having a gitlab_projects subprocess between gitlab-rails / sidekiq and
      any git subprocesses (e.g. for fork_project, fetch_remote, etc, calls), we can
      also manage these git processes more cleanly, and avoid sending SIGKILL to them
      28a98db7
    • Nick Thomas's avatar
      Import gitlab_projects.rb from gitlab-shell · 4b785df2
      Nick Thomas authored
      By importing this Ruby code into gitlab-rails (and gitaly-ruby), we avoid
      200ms of startup time for each gitlab_projects subprocess we are eliminating.
      
      By not having a gitlab_projects subprocess between gitlab-rails / sidekiq and
      any git subprocesses (e.g. for fork_project, fetch_remote, etc, calls), we can
      also manage these git processes more cleanly, and avoid sending SIGKILL to them
      4b785df2