BigW Consortium Gitlab

  1. 20 Apr, 2016 6 commits
  2. 19 Apr, 2016 2 commits
  3. 14 Apr, 2016 1 commit
  4. 12 Apr, 2016 2 commits
    • Refactor `Issue#related_branches` · 5d88de09
      Timothy Andrew authored
      - Previously, the controller held the logic to calculate
        related branches, which was:
      
        `<branches ending with `issue.iid`> - <branches with a merge request referenced in the current issue>`
      
      - This logic belongs in the `related_branches` method, not in the
        controller. This commit makes this change.
      
      - This means that `Issue#related_branches` now needs to take a `User`.
        When we find the branches that have a merge request referenced in the
        current issue, this is limited to merge requests that the current user
        has access to.
      
      - This is not directly related to #14566, but is a related refactoring.
    • Sanitize branch names for confidential issues. · 377b59da
      Timothy Andrew authored
      - When creating new branches for confidential issues,
        prefer a branch name like `issue-15` to
        `some-sensitive-issue-title-15`.
      - The behaviour for non-confidential issues stays the same.
  5. 01 Apr, 2016 1 commit
  6. 23 Mar, 2016 1 commit
  7. 20 Mar, 2016 1 commit
  8. 19 Mar, 2016 3 commits
  9. 18 Mar, 2016 1 commit
    • \#to_branch_name now uses the iid as postfix · 70ca3370
      Zeger-Jan van de Weg authored
      Given the branch name 'mep-mep' with an iid being 1,
      the current way, master's way, would yield a branch name of
      1-mep-mep. The problem for larger projects however would be that
      a developer might forget what iid the issue was.
      
      When this developer would try to tab complete it would:
      - Or result in 20+ branches possibly
      - Or start with the wrong digit, try again with digit++
        - Would see 20 branches, repeat
      
      Thus the obvious way of solving this is letting the dev tab complete
      on the issue title, which is easier to remember.
  10. 17 Mar, 2016 4 commits
  11. 15 Mar, 2016 4 commits
  12. 22 Jan, 2016 1 commit
  13. 13 Jan, 2016 1 commit
  14. 07 Jan, 2016 2 commits
  15. 21 Dec, 2015 1 commit
  16. 15 Dec, 2015 2 commits
  17. 11 Dec, 2015 1 commit
  18. 01 Dec, 2015 1 commit
  19. 30 Nov, 2015 1 commit
  20. 16 Oct, 2015 2 commits
  21. 06 Sep, 2015 1 commit
  22. 26 May, 2015 1 commit