An error occurred fetching the project authors.
  1. 12 Jan, 2017 1 commit
  2. 15 Nov, 2016 1 commit
    • Yar's avatar
      Unify anchor link format for MR diff files !7298 · 8782bb96
      Yar authored
      Right now, the following naming scheme for diff files is used: diff-1, diff-2, ... and also we have "internal" format which is file-path-HASH, where HASH is sha1 of file path.
      Besides, we have HASH_lineA_lineB format to link exact line number in MR diff. It makes sence to unify the way we link diff from outside, while leave "file-path-HASH" format for internal (js) usage.
      Changes in this commit  allow to link diff just by HASH, if we don't want specify exact lines, also it changes "file-path-HASH" and "diff-NUMBER" links in code to this unified format.
      
      Inspired by #24010 and !7298
      8782bb96
  3. 06 Oct, 2016 1 commit
  4. 20 Sep, 2016 1 commit
  5. 04 Aug, 2016 2 commits
  6. 03 Aug, 2016 3 commits
  7. 26 Jul, 2016 1 commit
    • Sean McGivern's avatar
      Fix expand all diffs button in compare view · 3abffb2b
      Sean McGivern authored
      We can't reuse the existing value of the format parameter, because on
      the merge request page that's 'json', so the link would go to a JSON
      file. We can't set it to HTML, because that adds '.html' the URL, which
      breaks the compare view (and looks bad). Setting it to nil uses the
      default format, which in all of these cases is HTML anyway.
      3abffb2b
  8. 18 Jul, 2016 1 commit
  9. 08 Jul, 2016 2 commits
  10. 06 Jul, 2016 5 commits
  11. 16 Jun, 2016 2 commits
  12. 12 Jun, 2016 1 commit
    • Stan Hu's avatar
      Fix Error 500 when viewing a blob with binary characters after the 1024-byte mark · 0fdfd2dd
      Stan Hu authored
      Here was the problem:
      
      1. When determining whether a given blob is viewable text, gitlab_git reads the first 1024 bytes and checks with Linguist whether it is a text or binary file.
      2. If the blob is text, GitLab will attempt to display it.
      3. However, if the text has binary characters after the first 1024 bytes, then GitLab will attempt to load the entire contents, but the encoding will be ASCII-8BIT since there are binary characters.
      4. The Error 500 results when GitLab attempts to display a mix UTF-8 and ASCII-8BIT.
      
      To fix this, we load as much data as we are willing to display so that the detection will work properly. Requires
      an update to gitlab_git: gitlab-org/gitlab_git!86
      
      Closes #13826
      0fdfd2dd
  13. 10 Jun, 2016 1 commit
  14. 26 Apr, 2016 4 commits
  15. 07 Apr, 2016 1 commit
  16. 19 Mar, 2016 1 commit
  17. 03 Mar, 2016 1 commit
  18. 14 Jan, 2016 2 commits
  19. 08 Jan, 2016 1 commit
  20. 02 Dec, 2015 1 commit
  21. 17 Nov, 2015 1 commit
  22. 06 Nov, 2015 1 commit
  23. 20 Oct, 2015 1 commit
  24. 01 Oct, 2015 2 commits
  25. 30 Sep, 2015 1 commit
  26. 08 Sep, 2015 1 commit