1. 07 2月, 2018 2 次提交
    • Z
      Don't use rugged in Repository#refs_hash · 73e78c4e
      Zeger-Jan van de Weg 提交于
      The refs hash is used to determine what branches and tags have a commit
      as head in the network graph. The previous implementation depended on
      Rugged#references. The problem with this implementation was that it
      depended on rugged, but also that it iterated over all references and
      thus loading more data than needed if for example the project uses CI/CD
      environments, Pipelines, or Merge Requests.
      
      Given only refs are checked the network cares about the GraphHelper#refs
      method has no need to reject those, simplifying the method.
      
      Closes gitlab-org/gitaly#880
      73e78c4e
    • B
      285d5d52
  2. 03 2月, 2018 2 次提交
  3. 02 2月, 2018 1 次提交
  4. 01 2月, 2018 3 次提交
    • Z
      fd46d6ce
    • Z
      Client changes for Tag,BranchNamesContainingCommit · 0a47d192
      Zeger-Jan van de Weg 提交于
      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.
      0a47d192
    • T
      Enable RuboCop Style/RegexpLiteral · 2b6307f6
      Takuya Noguchi 提交于
      2b6307f6
  5. 31 1月, 2018 5 次提交
  6. 30 1月, 2018 1 次提交
  7. 29 1月, 2018 2 次提交
  8. 25 1月, 2018 6 次提交
  9. 24 1月, 2018 2 次提交
  10. 23 1月, 2018 1 次提交
  11. 22 1月, 2018 1 次提交
  12. 20 1月, 2018 1 次提交
  13. 19 1月, 2018 2 次提交
  14. 18 1月, 2018 1 次提交
  15. 17 1月, 2018 1 次提交
  16. 12 1月, 2018 1 次提交
  17. 11 1月, 2018 1 次提交
  18. 10 1月, 2018 2 次提交
  19. 09 1月, 2018 1 次提交
  20. 07 1月, 2018 1 次提交
    • S
      Fix error 500 when viewing commit and merge request diffs · c2b7147c
      Stan Hu 提交于
      Due to the refactoring in !16082, `Blob#batch` no longer falls back
      to a default `blob_size_limit`. Since `Repository#batch_blobs` was using
      a default `nil` value, this would cause issues in the `Blob#find_by_rugged`
      method.
      
      This fix here is to be consistent and use a non-nil default value in
      `Repository#batch_blobs`.
      
      The problem was masked in development and tests because Gitaly is always
      enabled by default for all features.
      
      Closes #41735
      c2b7147c
  21. 06 1月, 2018 3 次提交