An error occurred fetching the project authors.
- 25 Apr, 2018 1 commit
-
-
Zeger-Jan van de Weg authored
Has been in opt out for 5 months, and within GitLab been in production for longer than that. No code needs to be migrated as this is implemented in GoLang over at Gitaly. Closes https://gitlab.com/gitlab-org/gitaly/issues/314
-
- 19 Apr, 2018 1 commit
-
-
Nick Thomas authored
-
- 14 Apr, 2018 3 commits
-
-
Stan Hu authored
-
Stan Hu authored
-
Stan Hu authored
This is called repeatedly when viewing a merge request, and this should improve performance significantly by avoiding shelling out to git every time. This should help https://gitlab.com/gitlab-com/infrastructure/issues/4027.
-
- 13 Apr, 2018 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 12 Apr, 2018 3 commits
-
-
Zeger-Jan van de Weg authored
Direct disk access is impossible on environments where components run in their own container. There for constructing the path should not be done except for exceptional cases. One of the considerations, instead of logging, was to use Sentry. For now I've chosen not to use this as the impact of this change is hard to determine. Getting this in now will allow us to checkout the impact on dev.gitlab.org and staging.
-
Zeger-Jan van de Weg authored
Part of the Gitaly migration as tracked in: https://gitlab.com/gitlab-org/gitaly/issues/401 Acceptance testing was done in: https://gitlab.com/gitlab-org/gitaly/issues/1014
-
Rubén Dávila authored
-
- 11 Apr, 2018 3 commits
-
-
Zeger-Jan van de Weg authored
Clients can now request the attributes from `$GIT_DIR/info/attributes` through Gitaly. The Gitaly migration is described in gitlab-org/gitaly#1082. The parser algorithm was implemented in a way it could handle both file contents or a File handle, and both were already tested. Other than that, using the boy scout rule, I've removed a class, InfoAttributes, as it was delegating everything to the parser and therefor wasn't really needed in my opinion.
-
Zeger-Jan van de Weg authored
By default this was an OPT_IN RPC, and now graduates to OPT_OUT as the acceptance testing was successful in: gitaly#1009 This follows the conventions of our [migration process](https://gitlab.com/gitlab-org/gitaly/blob/master/doc/MIGRATION_PROCESS.md)
-
Zeger-Jan van de Weg authored
By default this was an OPT_IN RPC, and now graduates to OPT_OUT as the acceptance testing was successful in: https://gitlab.com/gitlab-org/gitaly/issues/1008 This follows the conventions of our [migration process](https://gitlab.com/gitlab-org/gitaly/blob/master/doc/MIGRATION_PROCESS.md)
-
- 06 Apr, 2018 4 commits
-
-
Douglas Barbosa Alexandre authored
-
Stan Hu authored
git 2.16 will fail badly if there are stale worktrees. Closes #44115
-
Zeger-Jan van de Weg authored
Acceptance testing was successful in https://gitlab.com/gitlab-org/gitaly/issues/1058. So this is moved to OPT OUT. Part of https://gitlab.com/gitlab-org/gitaly/issues/1026
-
James Ramsay authored
Repository archives are always named `<project>-<ref>-<sha>` even if the ref is a commit. A consequence of always including the sha even for tags is that packaging a release is more difficult because both the ref and sha must be known by the packager. - add `<project>/-/archive/<ref>/<filename>.<format>` route using the `-` separator to prevent namespace collisions. If the filename is `<project>-<ref>` or the ref is a sha, the sha will be omitted, otherwise the default filename will be used. - deprecate previous archive route `repository/<ref>/archive`
-
- 04 Apr, 2018 2 commits
-
-
James Ramsay authored
Repository archives are always named `<project>-<ref>-<sha>` even if the ref is a commit. A consequence of always including the sha even for tags is that packaging a release is more difficult because both the ref and sha must be known by the packager. - add append_sha option (defaults true) to provide a method for toggling this feature. Support added to GitLab Workhorse by gitlab-org/gitlab-workhorse!232
-
Zeger-Jan van de Weg authored
Has been stable for a while in production, so this endpoint grew out if OPT_IN, the default state. Part of https://gitlab.com/gitlab-org/gitaly/issues/526
-
- 03 Apr, 2018 1 commit
-
-
Ahmad Sherif authored
Closes gitaly#1110
-
- 30 Mar, 2018 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 27 Mar, 2018 1 commit
-
-
Douwe Maan authored
-
- 22 Mar, 2018 1 commit
-
-
Alejandro Rodríguez authored
Before we were using a "plumbing" Gitlab::Git method that does not go through Gitaly migration checking.
-
- 21 Mar, 2018 1 commit
-
-
Jacob Vosmaer authored
-
- 19 Mar, 2018 1 commit
-
-
Jasper Maes authored
Split repository search result on \n instead of $ to prevent the items of the array to start with a newline. Remove the strip from parsing the search result to keep result endlines.
-
- 15 Mar, 2018 1 commit
-
-
James Edwards-Jones authored
Prevents `.gitattributes` blob lookup being repeated for every file checked at a given ref
-
- 08 Mar, 2018 2 commits
-
-
Kim "BKC" Carlbäcker authored
-
Jacob Vosmaer authored
-
- 07 Mar, 2018 8 commits
-
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#476
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#476
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitlab-ce!17561
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#540
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#546
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#779
-
Zeger-Jan van de Weg authored
Part of: gitlab-org/gitaly#541
-
Zeger-Jan van de Weg authored
Part of gitlab-org/gitaly#616
-
- 06 Mar, 2018 1 commit
-
-
Ahmad Sherif authored
Fixes gitaly#1057 The old code was calling LastCommitForPath to extract a commit ID _then_ call FindCommit to get a commit it already had in the first place!
-
- 02 Mar, 2018 1 commit
-
-
Ahmad Sherif authored
-
- 01 Mar, 2018 2 commits
-
-
Zeger-Jan van de Weg authored
Part of the migration as tracked in: gitlab-org/gitaly#1026
-
Tiago Botelho authored
-
- 26 Feb, 2018 1 commit
-
-
Sean McGivern authored
These are obscuring the real error, which is confusing for everyone.
-