BigW Consortium Gitlab

  1. 05 Jul, 2017 8 commits
  2. 03 Jul, 2017 1 commit
  3. 30 Jun, 2017 1 commit
    • Implement review comments for !12445 from @godfat and @rymai. · 3c88a786
      Timothy Andrew authored
      - Use `GlobalPolicy` to authorize the users that a non-authenticated user can
        fetch from `/api/v4/users`. We allow access if the `Gitlab::VisibilityLevel::PUBLIC`
        visibility level is not restricted.
      
      - Further, as before, `/api/v4/users` is only accessible to unauthenticated users if
        the `username` parameter is passed.
      
      - Turn off `authenticate!` for the `/api/v4/users` endpoint by matching on the actual
        route + method, rather than the description.
      
      - Change the type of `current_user` check in `UsersFinder` to be more
        compatible with EE.
  4. 29 Jun, 2017 1 commit
  5. 27 Jun, 2017 1 commit
  6. 15 Jun, 2017 1 commit
  7. 13 Jun, 2017 1 commit
  8. 08 Jun, 2017 3 commits
    • Merge branch '25934-project-snippet-vis' into 'security-9-2' · ae6adf16
      DJ Mountney authored
      Fix visibility when referencing snippets
      
      See merge request !2101
    • Bring in security changes from the 9.2.5 release · 565ead61
      DJ Mountney authored
      Ran:
       - git format-patch v9.2.2..v9.2.5 --stdout > patchfile.patch
       - git checkout -b 9-2-5-security-patch origin/v9.2.2
       - git apply patchfile.patch
       - git commit
       - [Got the sha ref for the commit]
       - git checkout -b upstream-9-2-security master
       - git cherry-pick <SHA of the patchfile commit>
       - [Resolved conflicts]
       - git cherry-pick --continue
    • Bring in security changes from the 9.2.5 release · 1d1363e2
      DJ Mountney authored
      Ran:
       - git format-patch v9.2.2..v9.2.5 --stdout > patchfile.patch
       - git checkout -b 9-2-5-security-patch origin/v9.2.2
       - git apply patchfile.patch
       - git commit
       - [Got the sha ref for the commit]
       - git checkout -b upstream-9-2-security master
       - git cherry-pick <SHA of the patchfile commit>
       - [Resolved conflicts]
       - git cherry-pick --continue
  9. 05 Jun, 2017 1 commit
    • Allow group reporters to manage group labels · 5db229fb
      Sean McGivern authored
      Previously, only group masters could do this. However, project reporters can
      manage project labels, so there doesn't seem to be any need to restrict group
      labels further.
      
      Also, save a query or two by getting a single GroupMember object to find out if
      the user is a master or not.
  10. 02 Jun, 2017 1 commit
  11. 31 May, 2017 1 commit
  12. 10 May, 2017 1 commit
  13. 08 May, 2017 1 commit
  14. 07 May, 2017 1 commit
  15. 05 May, 2017 1 commit
  16. 03 May, 2017 1 commit
  17. 02 May, 2017 1 commit
  18. 01 May, 2017 2 commits
  19. 26 Apr, 2017 1 commit
  20. 12 Apr, 2017 3 commits
  21. 11 Apr, 2017 1 commit
  22. 09 Apr, 2017 1 commit
  23. 07 Apr, 2017 1 commit
  24. 06 Apr, 2017 1 commit
    • ProjectsFinder should handle more options · b996a82f
      Jacopo authored
      Extended ProjectFinder in order to handle the following options:
       - current_user - which user use
       - project_ids_relation: int[] - project ids to use
       - params:
         -  trending: boolean
         -  non_public: boolean
         -  starred: boolean
         -  sort: string
         -  visibility_level: int
         -  tags: string[]
         -  personal: boolean
         -  search: string
         -  non_archived: boolean
      
      GroupProjectsFinder now inherits from ProjectsFinder.
      Changed the code in order to use the new available options.
  25. 09 Mar, 2017 4 commits