1. 07 12月, 2016 1 次提交
  2. 01 12月, 2016 1 次提交
  3. 01 11月, 2016 1 次提交
  4. 28 10月, 2016 1 次提交
  5. 23 9月, 2016 1 次提交
  6. 19 9月, 2016 1 次提交
    • N
      Enable Warden for the Grape API · 10c07226
      Nick Thomas 提交于
      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
      10c07226
  7. 25 8月, 2016 1 次提交
  8. 09 8月, 2016 1 次提交
  9. 19 7月, 2016 1 次提交
  10. 18 7月, 2016 1 次提交
  11. 14 7月, 2016 1 次提交
  12. 13 7月, 2016 1 次提交
    • T
      Refactor `Gitlab::GitAccess` · 60245bbe
      Timothy Andrew 提交于
      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
      60245bbe
  13. 02 7月, 2016 1 次提交
  14. 16 6月, 2016 1 次提交
  15. 29 4月, 2016 3 次提交
  16. 23 10月, 2015 1 次提交
  17. 22 6月, 2015 2 次提交
  18. 13 2月, 2015 1 次提交
  19. 24 12月, 2014 1 次提交
  20. 15 5月, 2014 3 次提交
  21. 12 4月, 2014 1 次提交
  22. 10 9月, 2013 3 次提交