Timothy Andrew 5d88de092f Refactor Issue#related_branches ...

- 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.

2016-04-12 11:43:15 +05:30

..

assets

Merge branch 'fix-revert-scroll' into 'master'

2016-04-11 16:12:28 +00:00

controllers

Refactor Issue#related_branches

2016-04-12 11:43:15 +05:30

finders

Standardised the output of the JSON to always include the name

2016-03-29 11:59:13 +01:00

helpers

Merge branch 'issue_1752' into 'master'

2016-04-11 23:26:45 +00:00

mailers

Improve and finish the fallback to the In-Reply-To and References header for the reply-by-email feature

2016-03-25 13:05:15 +01:00

models

Refactor Issue#related_branches

2016-04-12 11:43:15 +05:30

services

Merge branch 'issue_14012' into 'master'

2016-04-07 15:19:56 +00:00

uploaders

Remove reduntant move_to_store override

2016-03-30 12:50:19 +02:00

validators

Allow webhooks URL to have leading and trailing spaces

2016-02-26 14:34:06 -05:00

views

Merge branch 'rs-form_errors' into 'master'

2016-04-11 12:01:50 +00:00

workers

Exclude projects pending deletion from all results

2016-03-31 20:20:18 +02:00