An error occurred fetching the project authors.
- 14 Nov, 2016 1 commit
-
-
Robert Schilling authored
-
- 01 Nov, 2016 1 commit
-
-
Felipe Artur authored
-
- 27 Oct, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 19 Oct, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 06 Oct, 2016 2 commits
-
-
Justin DiPierro authored
-
Nick Thomas authored
Per https://gitlab.com/gitlab-org/gitlab-ce/issues/22820, this helper is mixed in to classes that lack a `request` method. They do include `env`, so use it instead.
-
- 23 Sep, 2016 1 commit
-
-
Nick Thomas authored
-
- 19 Sep, 2016 1 commit
-
-
Nick Thomas authored
The practical effect of this commit is to make the API check the Rails session cookie for authentication details. If the cookie is present and valid, it will be used to authenticate. The API now has several authentication options for users. They follow in this order of precedence: * Authentication token * Personal access token * OAuth2 Bearer token (Doorkeeper - application access) * Rails session cookie
-
- 13 Sep, 2016 1 commit
-
-
Tomasz Maczukin authored
-
- 30 Aug, 2016 5 commits
-
-
http://jneen.net/ authored
-
http://jneen.net/ authored
-
http://jneen.net/ authored
-
tiagonbotelho authored
-
tiagonbotelho authored
-
- 24 Aug, 2016 1 commit
-
-
Stan Hu authored
Closes #21043
-
- 18 Aug, 2016 3 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
-
Patricio Cano authored
Added checks for 2FA to the API `/sessions` endpoint and the Resource Owner Password Credentials flow.
-
- 10 Aug, 2016 2 commits
-
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Also, mutualize AccessRequests and Members endpoints for Group & Project. New API documentation for the AccessRequests endpoints. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 20 Jul, 2016 1 commit
-
-
Robert Schilling authored
-
- 19 Jul, 2016 1 commit
-
-
Robert Schilling authored
-
- 18 Jul, 2016 1 commit
-
-
Rémy Coutable authored
This reverts commit 530f5158. See !4892. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
- 13 Jul, 2016 2 commits
-
-
Robert Speicher authored
This reverts commit 9ca633eb, reversing changes made to fb229bbf.
-
Timothy Andrew authored
1. Don't use case statements for dispatch anymore. This leads to a lot of duplication, and makes the logic harder to follow. 2. Remove duplicated logic. - For example, the `can_push_to_branch?` exists, but we also have a different way of checking the same condition within `change_access_check`. - This kind of duplication is removed, and the `can_push_to_branch?` method is used in both places. 3. Move checks returning true/false to `UserAccess`. - All public methods in `GitAccess` now return an instance of `GitAccessStatus`. Previously, some methods would return true/false as well, which was confusing. - It makes sense for these kinds of checks to be at the level of a user, so the `UserAccess` class was repurposed for this. The prior `UserAccess.allowed?` classmethod is converted into an instance method. - All external uses of these checks have been migrated to use the `UserAccess` class 4. Move the "change_access_check" into a separate class. - Create the `GitAccess::ChangeAccessCheck` class to run these checks, which are quite substantial. - `ChangeAccessCheck` returns an instance of `GitAccessStatus` as well. 5. Break out the boolean logic in `ChangeAccessCheck` into `if/else` chains - this seems more readable. 6. I can understand that this might look like overkill for !4892, but I think this is a good opportunity to clean it up. - http://martinfowler.com/bliki/OpportunisticRefactoring.html
-
- 12 Jul, 2016 4 commits
-
-
tiagonbotelho authored
-
tiagonbotelho authored
-
tiagonbotelho authored
-
tiagonbotelho authored
-
- 06 Jul, 2016 2 commits
-
-
tiagonbotelho authored
-
tiagonbotelho authored
-
- 16 Jun, 2016 1 commit
-
-
Timothy Andrew authored
- Extract a duplicated `redirect_to` - Fix a typo: "token", not "certificate" - Have the "Expires at" datepicker be attached to a text field, not inline - Have both private tokens and personal access tokens verified in a single "authenticate_from_private_token" method, both in the application and API. Move relevant logic to `User#find_by_personal_access_token` - Remove unnecessary constants relating to API auth. We don't need a separate constant for personal access tokens since the param is the same as for private tokens.
-
- 12 Jun, 2016 1 commit
-
-
Stan Hu authored
Closes #18484
-
- 10 Jun, 2016 1 commit
-
-
Douwe Maan authored
-
- 06 Jun, 2016 1 commit
-
-
Douwe Maan authored
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 23 May, 2016 1 commit
-
-
Robert Speicher authored
-
- 18 May, 2016 1 commit
-
-
Felipe Artur authored
-
- 16 May, 2016 1 commit
-
-
Felipe Artur authored
-