Read about our upcoming Code of Conduct on this issue

  1. 07 Apr, 2018 2 commits
  2. 06 Apr, 2018 1 commit
  3. 05 Apr, 2018 1 commit
  4. 28 Mar, 2018 1 commit
    • Bob Van Landuyt's avatar
      Remove permanent redirects · a2921cadb78e
      Bob Van Landuyt authored
      Removes permanent redirects, this means that redirects will only be
      possible as long as the old route isn't taken by a new project/group.
  5. 25 Feb, 2018 1 commit
  6. 15 Feb, 2018 1 commit
  7. 06 Feb, 2018 6 commits
  8. 17 Jan, 2018 1 commit
  9. 22 Dec, 2017 1 commit
  10. 08 Dec, 2017 1 commit
  11. 07 Oct, 2017 1 commit
    • Jacopo's avatar
      Replaces `tag: true` into `:tag` in the specs · f4ef7328afe4
      Jacopo authored
      Replaces all the explicit include metadata syntax in the specs (tag:
      true) into the implicit one (:tag).
      Added a cop to prevent future errors and handle autocorrection.
  12. 06 Oct, 2017 1 commit
    • Toon Claes's avatar
      Create idea of read-only database · a867cd2b92f4
      Toon Claes authored
      In GitLab EE, a GitLab instance can be read-only (e.g. when it's a Geo
      secondary node). But in GitLab CE it also might be useful to have the
      "read-only" idea around. So port it back to GitLab CE.
      Also having the principle of read-only in GitLab CE would hopefully
      lead to less errors introduced, doing write operations when there
      aren't allowed for read-only calls.
      Closes gitlab-org/gitlab-ce#37534.
  13. 30 Aug, 2017 3 commits
    • Nick Thomas's avatar
      Address review comments · dab95b4ab93e
      Nick Thomas authored
    • Nick Thomas's avatar
      Rework the permissions model for SSH key restrictions · e61111a36891
      Nick Thomas authored
      `allowed_key_types` is removed and the `minimum_<type>_bits` fields are
      renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies
      that the key type is disabled.
      This also feeds through to the UI - checkboxes per key type are out, inline
      selection of "forbidden" and "allowed" (i.e., no restrictions) are in.
      As with the previous model, unknown key types are disallowed, even if the
      underlying ssh daemon happens to support them. The defaults have also been
      changed from the lowest known bit size to "no restriction". So if someone
      does happen to have a 768-bit RSA key, it will continue to work on upgrade, at
      least until the administrator restricts them.
    • Nick Thomas's avatar
      Add settings for minimum key strength and allowed key type · 769b454c7135
      Nick Thomas authored
      This is an amalgamation of:
      * Cory Hinshaw: Initial implementation !5552
      * Rémy Coutable: Updates !9350
      * Nick Thomas: Resolve conflicts and add ED25519 support !13712
  14. 23 Aug, 2017 1 commit
  15. 18 Aug, 2017 2 commits
    • Robert Speicher's avatar
      Reduce duplication in GitAccess spec around error messages · c7bad8d66b42
      Robert Speicher authored
      - Adds a new `ProjectMovedError` class to encapsulate that error
        condition. Inherits from `NotFoundError` so existing rescues should
        continue to work.
      - Separating that condition out of `NotFoundError` allowed us to
        simplify the `raise_not_found` helper and avoid repeating the literal
      - Spec makes use of `ERROR_MESSAGES` hash to avoid repeating literal
        error message strings.
    • Robert Speicher's avatar
      Greatly reduce test duration for git_access_spec · ca7970c9da9b
      Robert Speicher authored
      - Combine multiple `it` blocks into one where it made sense
      - Use `set` for the top-level User record
      - Refactor permission matrix tests
  16. 27 Jul, 2017 2 commits
  17. 16 Jun, 2017 1 commit
  18. 14 Jun, 2017 1 commit
  19. 05 Jun, 2017 5 commits
  20. 08 May, 2017 1 commit
  21. 20 Apr, 2017 1 commit
  22. 03 Apr, 2017 1 commit
  23. 24 Feb, 2017 1 commit
  24. 23 Feb, 2017 2 commits
    • Douwe Maan's avatar
      Enable Style/WordArray · e295189744bb
      Douwe Maan authored
    • Sean McGivern's avatar
      Fix GitAccess specs · 5f8d59b12c27
      Sean McGivern authored
      These specs never ran due to incorrect indentation: the `context` blocks
      were inside the `before`.
      Additionally, `GitHooksService` now has to yield itself to callers, and
      `GitAccess` never appears to have had an `allowed?` method.
  25. 05 Feb, 2017 1 commit