- 06 Feb, 2018 5 commits
-
-
Tiago Botelho authored
-
Tiago Botelho authored
-
Tiago Botelho authored
-
Tiago Botelho authored
-
Tiago Botelho authored
-
- 22 Jan, 2018 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 29 Nov, 2017 1 commit
-
-
Kim "BKC" Carlbäcker authored
- Better gitaly-handling in /api/internal/allowed specs
-
- 22 Nov, 2017 1 commit
-
-
Lin Jen-Shin authored
And use .rubocop.yml to exclude paths we don't care, rather than using the cop itself to exclude.
-
- 17 Nov, 2017 1 commit
-
-
Lin Jen-Shin authored
-
- 14 Nov, 2017 1 commit
-
-
Ahmad Sherif authored
-
- 18 Sep, 2017 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 05 Sep, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 31 Aug, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 07 Jul, 2017 1 commit
-
-
Kim "BKC" Carlbäcker authored
- Make single gitaly payload - Add feature-flag specs to verify payload
-
- 16 Jun, 2017 1 commit
-
-
Michael Kozono authored
-
- 05 Jun, 2017 1 commit
-
-
Michael Kozono authored
-
- 03 May, 2017 1 commit
-
-
Alejandro Rodríguez authored
This new param allows us to share project information between components that don't share or don't have access to the same filesystem mountpoints, for example between Gitaly and Rails or between Rails and Gitlab-Shell hooks. The previous parameters are still supported, but if found, gl_repository is prefered. The old parameters should be deprecated once all components support the new format.
-
- 14 Apr, 2017 2 commits
-
-
Sean McGivern authored
-
James Lopez authored
Refactored specs and added a post deployment migration to remove the activity users table.
-
- 10 Apr, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 03 Mar, 2017 1 commit
-
-
Alejandro Rodríguez authored
This will be necessary when adding gitaly settings. This version doesn't make any functional changes, but allows us to include this breaking change in 9.0 and add the needed extra settings in the future with backwards compatibility
-
- 03 Feb, 2017 1 commit
-
-
Adam Pahlevi authored
add complete changelog for !8949
-
- 16 Dec, 2016 1 commit
-
-
Timothy Andrew authored
1. Starting version 2.11, git changed the way the pre-receive flow works. - Previously, the new potential objects would be added to the main repo. If the pre-receive passes, the new objects stay in the repo but are linked up. If the pre-receive fails, the new objects stay orphaned in the repo, and are cleaned up during the next `git gc`. - In 2.11, the new potential objects are added to a temporary "alternate object directory", that git creates for this purpose. If the pre-receive passes, the objects from the alternate object directory are migrated to the main repo. If the pre-receive fails the alternate object directory is simply deleted. 2. In our workflow, the pre-recieve script (in `gitlab-shell) calls the `/allowed` endpoint, which calls out directly to git to perform various checks. These direct calls to git do _not_ have the necessary environment variables set which allow access to the "alternate object directory" (explained above). Therefore these calls to git are not able to access any of the new potential objects to be added during this push. 3. We fix this by accepting the relevant environment variables (GIT_ALTERNATE_OBJECT_DIRECTORIES, GIT_OBJECT_DIRECTORY) on the `/allowed` endpoint, and then include these environment variables while calling out to git. 4. This commit includes (whitelisted) these environment variables while making the "force push" check. A `Gitlab::Git::RevList` module is extracted to prevent `ForcePush` from being littered with these checks.
-
- 16 Nov, 2016 1 commit
-
-
Nick Thomas authored
gitlab-shell v3.6.6 would give project paths like so: * namespace/project gitlab-shell v4.0.0 can give project paths like so: * /namespace1/namespace2/project * /namespace/project * /path/to/repository/storage/namespace1/namespace2/project * /path/to/repository/storage/namespace/project
-