An error occurred fetching the project authors.
- 14 Jul, 2017 1 commit
-
-
Stan Hu authored
Somehow Rails.cache.fetch occasionally returns `nil` values, which causes this endpoint to crash. Closes #35094
-
- 07 Jul, 2017 1 commit
-
-
Kim "BKC" Carlbäcker authored
- Make single gitaly payload - Add feature-flag specs to verify payload
-
- 23 Jun, 2017 7 commits
-
-
James Lopez authored
# Conflicts: # app/controllers/admin/users_controller.rb
-
James Lopez authored
fix spec added bang option to spec use update service on ldap call and updated specs and service update profiles controller to use new service refactor profiles controller and update service update users controller finish off refactoring users controller fix profiles controller updated emails, notifications and passwords controller update preferences controller update notification settings, fix api specs fix specs fix api and controller issues added service in the rest of controllers and classes add emails service specs add more spec examples add create and destroy services for emails fixed specs update to use emails destroy service fix specs update missing email actions add missing user updates refactor emails service more refactoring based on feedback add missing action to block more refactoring fix spec failures fix specs refactor update user service not to do auth checks
-
James Lopez authored
-
Nick Thomas authored
-
James Lopez authored
-
James Lopez authored
-
James Lopez authored
-
- 20 Jun, 2017 1 commit
-
-
Matt Walsh authored
-
- 17 Jun, 2017 1 commit
-
-
Michael Kozono authored
-
- 16 Jun, 2017 1 commit
-
-
Michael Kozono authored
-
- 15 Jun, 2017 1 commit
-
-
Mike Ricketts authored
-
- 07 Jun, 2017 1 commit
-
-
Michael Kozono authored
-
- 05 Jun, 2017 3 commits
-
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
No external behavior change. This allows `GitHttpController` to set the HTTP status based on the type of error. Alternatively, we could have added an attribute to GitAccessStatus, but this pattern seemed appropriate.
-
- 18 May, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 10 May, 2017 2 commits
-
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 05 May, 2017 3 commits
-
-
Alejandro Rodríguez authored
-
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.
-
Alejandro Rodríguez 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.
-
- 27 Apr, 2017 1 commit
-
-
Luigi Leoni authored
-
- 14 Apr, 2017 2 commits
-
-
Sean McGivern authored
-
James Lopez authored
It uses a user activity table instead of a column in users. Tested with mySQL and postgreSQL
-
- 10 Apr, 2017 2 commits
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 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
-
- 28 Feb, 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 2 commits
-
-
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.
-
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.
-
- 17 Nov, 2016 1 commit
-
-
Alejandro Rodríguez authored
-
- 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>
-