- 07 Apr, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 04 Apr, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 29 Mar, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 01 Mar, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 08 Jan, 2017 1 commit
-
-
Vincent Wong authored
Addresses: Issue #13810 1. Adds a last_used_at attribute to the Key table/model 2. Update a key's last_used_at whenever it gets used 3. Display how long ago an ssh key was last used
-
- 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
-
- 28 Oct, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 27 Oct, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 28 Sep, 2016 1 commit
-
-
Patricio Cano authored
Reset expiry time of token, if token is retrieved again before it expires.
-
- 19 Sep, 2016 2 commits
-
-
Kamil Trzcinski authored
Revert "Revert all changes introduced by https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043" This reverts commit 6d43c95b.
-
- 16 Sep, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 15 Sep, 2016 7 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
-
Patricio Cano authored
Refactored LFS auth logic when using SSH to use its own API endpoint `/lfs_authenticate` and added tests.
-
Patricio Cano authored
-
Patricio Cano authored
- Required on the GitLab Rails side is mostly authentication and API related.
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 01 Sep, 2016 1 commit
-
-
Drew Blessing authored
-
- 24 Aug, 2016 1 commit
-
-
Drew Blessing authored
-
- 11 Aug, 2016 1 commit
-
-
Scott Le authored
DRY code + fix rubocop Add more test cases Append to changelog DRY changes list find_url service for merge_requests use GET for getting merge request links remove files rename to get_url_service reduce loop add test case for cross project refactor tiny thing update changelog
-
- 16 Jul, 2016 1 commit
-
-
Alejandro Rodríguez authored
-
- 05 Jul, 2016 1 commit
-
-
Patricio Cano authored
-
- 30 Jun, 2016 1 commit
-
-
Alejandro Rodríguez authored
-
- 18 Jun, 2016 1 commit
-
-
Paco Guzman authored
-
- 20 Apr, 2016 1 commit
-
-
Yorick Peterse authored
Merely setting the "action" tag will only result in the transaction itself containing a value for this tag. To ensure other metrics also contain this tag we must set the action using Transaction#action= instead.
-
- 18 Apr, 2016 1 commit
-
-
Yorick Peterse authored
This allows us to re-use any other analytics that rely on the "action" tag having a value set.
-
- 26 Feb, 2016 1 commit
-
-
James Lopez authored
-
- 24 Feb, 2016 1 commit
-
-
James Lopez authored
-
- 13 May, 2015 1 commit
-
-
Douwe Maan authored
-
- 24 Mar, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 02 Mar, 2015 1 commit
-
-
Douwe Maan authored
-
- 18 Feb, 2015 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 07 Feb, 2015 1 commit
-
-
Douwe Maan authored
-
- 03 Feb, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 28 Dec, 2014 1 commit
-
-
Ciro Santilli authored
and more readable.
-