An error occurred fetching the project authors.
  1. 05 Jun, 2018 2 commits
  2. 01 Jun, 2018 1 commit
  3. 30 May, 2018 1 commit
  4. 19 May, 2018 1 commit
  5. 18 May, 2018 1 commit
  6. 17 May, 2018 1 commit
  7. 14 May, 2018 1 commit
  8. 07 May, 2018 2 commits
  9. 30 Apr, 2018 2 commits
  10. 25 Apr, 2018 1 commit
  11. 14 Apr, 2018 2 commits
  12. 12 Apr, 2018 1 commit
  13. 06 Apr, 2018 3 commits
  14. 04 Apr, 2018 1 commit
    • James Ramsay's avatar
      Add option to suppress archive commit sha · 0b1b9c40
      James Ramsay authored
      Repository archives are always named `<project>-<ref>-<sha>` even if
      the ref is a commit. A consequence of always including the sha even
      for tags is that packaging a release is more difficult because both
      the ref and sha must be known by the packager.
      
      - add append_sha option (defaults true) to provide a method for
      toggling this feature.
      
      Support added to GitLab Workhorse by gitlab-org/gitlab-workhorse!232
      0b1b9c40
  15. 30 Mar, 2018 1 commit
  16. 27 Mar, 2018 1 commit
  17. 14 Mar, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Change Gitlab::Shell#add_namespace to #create_namespace · 77f0906e
      Zeger-Jan van de Weg authored
      Prior to this change, this method was called add_namespace, which broke
      the CRUD convention and made it harder to grep for what I was looking
      for. Given the change was a find and replace kind of fix, this was
      changed without opening an issue and on another feature branch.
      
      If more dynamic calls are made to add_namespace, these could've been
      missed which might lead to incorrect bahaviour. However, going through
      the commit log it seems thats not the case.
      77f0906e
  18. 02 Mar, 2018 1 commit
  19. 01 Mar, 2018 3 commits
  20. 26 Feb, 2018 1 commit
  21. 21 Feb, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Handle branch and tag names which are commit ids · e70fe782
      Zeger-Jan van de Weg authored
      Adds a test where a branch name is also a valid commit id. Git, the
      binary should create an error message which is difficult to parse and
      leading to errors later, as seen in: gitlab-org/gitlab-ce#43222
      
      To catch these cases in the future,
      gitlab-test@1942eed5cc108b19c7405106e81fa96125d0be22 was created. Which
      a branch name matching the commit
      e70fe782
  22. 20 Feb, 2018 1 commit
  23. 19 Feb, 2018 2 commits
    • Sean McGivern's avatar
      Fix squash with renamed files · 01f5035b
      Sean McGivern authored
      We need to ignore the names for renamed files when configuring with sparse
      checkout.
      01f5035b
    • Stan Hu's avatar
      Fix squash rebase not working when diff contained encoded data · 8d32dfef
      Stan Hu authored
      When the applied diff contains UTF-8 or some other encoded data, the diff
      returned back from the git process may be in ASCII-8BIT format. Writing this
      data to stdin may fail if the data because stdin expects this data to be in
      UTF-8. By switching the output to binmode, we ensure that the diff will
      always be written as-is.
      
      Closes gitlab-org/gitlab-ee#4960
      8d32dfef
  24. 07 Feb, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Don't use rugged in Repository#refs_hash · 73e78c4e
      Zeger-Jan van de Weg authored
      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
  25. 02 Feb, 2018 2 commits
  26. 01 Feb, 2018 1 commit
  27. 31 Jan, 2018 3 commits
  28. 30 Jan, 2018 1 commit