An error occurred fetching the project authors.
  1. 17 Feb, 2018 1 commit
  2. 14 Feb, 2018 4 commits
    • Stan Hu's avatar
      Remove head_commit call · 85068908
      Stan Hu authored
      85068908
    • Stan Hu's avatar
      Simplify license generator error handling · 5b3b2b82
      Stan Hu authored
      5b3b2b82
    • Stan Hu's avatar
      Remove use of catching Rugged exceptions · bc11af67
      Stan Hu authored
      bc11af67
    • Stan Hu's avatar
      Fix Error 500s loading repositories with no master branch · 35b3a0b9
      Stan Hu authored
      We removed the exception handling for Rugged errors in !16770, which
      revealed that the licensee gem attempts to retrieve a license file
      via Rugged in `refs/heads/master` by default. If that branch
      did not exist, a Rugged::ReferenceError would be thrown.
      
      There were two issues:
      
      1. Not every project uses `master` as the default branch. This
      change uses the head commit to identify the license.
      
      2. Removing the exception handling caused repositories to fail
      loading. We can safely catch and ignore any Rugged error because
      this means we weren't able to load a license file.
      
      Closes #43268
      35b3a0b9
  3. 07 Feb, 2018 1 commit
  4. 06 Feb, 2018 1 commit
  5. 02 Feb, 2018 1 commit
  6. 01 Feb, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Client changes for Tag,BranchNamesContainingCommit · 0a47d192
      Zeger-Jan van de Weg authored
      As part of gitlab-org/gitaly#884, this commit contains the client
      implementation for both TagNamesContaintingCommit and
      BranchNamesContainingCommit. The interface in the Repository model stays
      the same, but the implementation on the serverside, e.g. Gitaly, uses
      `for-each-ref`, as opposed to `branch` or `tag` which both aren't
      plumbing command. The result stays the same.
      
      On the serverside, we have the opportunity to limit the number of names
      to return. However, this is not supported on the front end yet. My
      proposal to use this ability: gitlab-org/gitlab-ce#42581. For now, this
      ability is not used as that would change more behaviours on a feature
      flag which might lead to unexpected changes on page refresh for example.
      Unverified
      0a47d192
  7. 30 Jan, 2018 4 commits
  8. 25 Jan, 2018 1 commit
  9. 24 Jan, 2018 2 commits
  10. 22 Jan, 2018 1 commit
  11. 18 Jan, 2018 1 commit
  12. 16 Jan, 2018 2 commits
  13. 15 Jan, 2018 4 commits
  14. 12 Jan, 2018 1 commit
  15. 11 Jan, 2018 2 commits
  16. 10 Jan, 2018 1 commit
  17. 09 Jan, 2018 1 commit
  18. 05 Jan, 2018 3 commits
  19. 22 Dec, 2017 1 commit
  20. 20 Dec, 2017 1 commit
  21. 19 Dec, 2017 1 commit
    • Zeger-Jan van de Weg's avatar
      Load commit in batches for pipelines#index · c6edae38
      Zeger-Jan van de Weg authored
      Uses `list_commits_by_oid` on the CommitService, to request the needed
      commits for pipelines. These commits are needed to display the user that
      created the commit and the commit title.
      
      This includes fixes for tests failing that depended on the commit
      being `nil`. However, now these are batch loaded, this doesn't happen
      anymore and the commits are an instance of BatchLoader.
      Unverified
      c6edae38
  22. 14 Dec, 2017 1 commit
  23. 13 Dec, 2017 2 commits
  24. 12 Dec, 2017 2 commits