An error occurred fetching the project authors.
  1. 12 Jul, 2019 1 commit
  2. 27 Jun, 2019 1 commit
  3. 14 Jun, 2019 1 commit
  4. 17 May, 2019 1 commit
    • Nick Thomas's avatar
      Use gitlab-elasticsearch-indexer in tests · c12754cc
      Nick Thomas authored
      The golang indexer is supplanting the Ruby one in GitLab 12.1, so it's
      important that we gain confidence in it by using it in the tests now.
      
      This should also help to expose problems and catch regressions earlier.
      c12754cc
  5. 16 May, 2019 1 commit
  6. 13 Mar, 2019 2 commits
  7. 27 Feb, 2019 1 commit
  8. 23 Feb, 2019 1 commit
  9. 23 Jan, 2019 1 commit
  10. 27 Dec, 2018 2 commits
  11. 07 Dec, 2018 1 commit
    • Mark Chao's avatar
      Update merge request's merge_commit for branch update · 1f7647f4
      Mark Chao authored
      Analyze new commits graph to determine each commit's merge commit.
      
      Fix "merged with [commit]" info for merge requests being merged
      automatically by other actions.
      
      Allow analyzing upto the relevant commit
      1f7647f4
  12. 07 Nov, 2018 4 commits
  13. 05 Nov, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Regenerate Gitaly's config.toml each rspec run · d49c617d
      Zeger-Jan van de Weg authored
      This behaviour I removed in 08cdf65b, but this reverts this specific
      line. In case storages, or other options changes which are set by the
      Rails environment, this will easier to migrate to.
      
      Storage paths is kept in plural, to support multiple storage in later
      release for just testing purposes. But its probable that multi Gitaly
      scenarios need to be tested.
      d49c617d
  14. 26 Oct, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Regenerate Gitaly's config.toml each rspec run · 6f4c1fd5
      Zeger-Jan van de Weg authored
      This behaviour I removed in 08cdf65b, but this reverts this specific
      line. In case storages, or other options changes which are set by the
      Rails environment, this will easier to migrate to.
      
      Storage paths is kept in plural, to support multiple storage in later
      release for just testing purposes. But its probable that multi Gitaly
      scenarios need to be tested.
      6f4c1fd5
  15. 24 Oct, 2018 2 commits
    • Zeger-Jan van de Weg's avatar
      Hotfix for Rspec and second storage · 176aabd8
      Zeger-Jan van de Weg authored
      Rails requires a second storage for testing cross shard features. Gitaly
      will not boot if this second storage doesn't exist. So this will create
      this storage without adding it to the list of storages that Rails knows
      about.
      176aabd8
    • Zeger-Jan van de Weg's avatar
      Hotfix for Rspec and second storage · 3efaf5b5
      Zeger-Jan van de Weg authored
      Rails requires a second storage for testing cross shard features. Gitaly
      will not boot if this second storage doesn't exist. So this will create
      this storage without adding it to the list of storages that Rails knows
      about.
      3efaf5b5
  16. 23 Oct, 2018 1 commit
  17. 18 Oct, 2018 1 commit
    • Alessio Caiazza's avatar
      Move ci_environments_status to a model · 4a9efc60
      Alessio Caiazza authored
      GET :namespace/merge_requests/:id/ci_environments_status complexity
      already reached a limit for a direct serialization from an hash
      computed at within the controller function.
      
      Here we introduce a virtual model EnvironmentStatus and its serializer.
      4a9efc60
  18. 17 Sep, 2018 2 commits
  19. 12 Sep, 2018 1 commit
  20. 06 Sep, 2018 2 commits
    • Bob Van Landuyt's avatar
      Allow specifying code owners in a CODEOWNERS file · dbde2b33
      Bob Van Landuyt authored
      In a file called `CODEOWNERS` in the root of a repository, in the
      `docs/`-folder or in the `.gitlab/` folder it is possible to define
      users that are 'owners' for specific code paths.
      
      A pattern can be defined on each line in the same way as it would in a
      `.gitignore` file. After that, one or more users can be specified
      using their username (using the `@username` format) or email address
      linked to their account. Comments can be preceded with a `#`. If a
      filename starts with `#` this can be escaped using `/#`.
      
      For example:
      
          # All files in the `docs/` directory should be reviewed by a
          # technical writer:
          docs/* @jane @joe
      
          # Ruby files should be reviewed by a backend maintainer:
          *.rb alice@development.gitlab.org
      
      The code owners will be displayed when viewing a blob, if a user for
      the username/email cannot be found, nothing will be shown.
      
      When multiple patterns match the blob being viewed, the last entry
      will be used.
      dbde2b33
    • Bob Van Landuyt's avatar
      Port changes for CODEOWNERS to CE · c826ecc3
      Bob Van Landuyt authored
      This ports the changes for the CODEOWNERS feature to CE:
      - It adds the CODEOWNERS file.
      - It adds the mention of the `with-codeowners` branch in TestEnv
      c826ecc3
  21. 12 Aug, 2018 1 commit
  22. 07 Aug, 2018 3 commits
  23. 31 Jul, 2018 1 commit
  24. 10 Jul, 2018 1 commit
  25. 12 Jun, 2018 1 commit
  26. 29 May, 2018 1 commit
  27. 14 May, 2018 1 commit
  28. 25 Apr, 2018 2 commits
  29. 23 Apr, 2018 1 commit