1. 23 Oct, 2017 1 commit
  2. 26 Sep, 2017 1 commit
  3. 15 Aug, 2017 1 commit
  4. 04 Aug, 2017 1 commit
  5. 03 Aug, 2017 2 commits
  6. 31 Jul, 2017 1 commit
  7. 28 Jul, 2017 1 commit
  8. 11 Jul, 2017 1 commit
  9. 05 Jul, 2017 1 commit
  10. 21 Jun, 2017 1 commit
  11. 09 Jun, 2017 1 commit
  12. 08 Jun, 2017 1 commit
  13. 07 Jun, 2017 1 commit
  14. 30 May, 2017 1 commit
  15. 17 May, 2017 1 commit
  16. 30 Apr, 2017 1 commit
  17. 27 Apr, 2017 3 commits
  18. 20 Apr, 2017 1 commit
  19. 06 Apr, 2017 1 commit
  20. 21 Mar, 2017 1 commit
  21. 13 Mar, 2017 1 commit
    • Jacopo's avatar
      New file from interface on existing branch · e0fe2834
      Jacopo authored
      Now you can create a new file and select a target_branch != source_branch.
      If the file that you want to create already exists on the target branch an error message is shown
      A glDropdown is used to select and create a new branch instead of a text field.
      e0fe2834
  22. 03 Mar, 2017 1 commit
  23. 01 Mar, 2017 1 commit
  24. 23 Feb, 2017 2 commits
  25. 21 Feb, 2017 1 commit
  26. 10 Feb, 2017 1 commit
  27. 07 Feb, 2017 1 commit
  28. 06 Feb, 2017 3 commits
  29. 29 Nov, 2016 3 commits
  30. 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
  31. 10 Sep, 2016 1 commit
  32. 15 Aug, 2016 1 commit
    • Frank West's avatar
      Prevents accidental overwrites of commits from UI · ade0c2c8
      Frank West authored
      Currently when a user performs an update of a file through the UI  and there
      has already been a change committed to the file the previous commits will be
      overwritten without a check to see if the file has been changed.
      
      This commit uses the last commit sha at the time the user starts editing the
      file and compares it with the current sha of the file being edited to ensure
      they are the same before committing the file. If the shas do not match we
      throw an exception preventing the commit from the commit from occurring.
      
      Fixes #5857
      ade0c2c8