gitlab-org--gitlab-foss/app/services/merge_requests
Bob Van Landuyt 8ad9c4e873 Rename `create_merge_request` permissions
So we can distinguish between the permissions on the source and the
target project.

- `create_merge_request_from` indicates a user can create a merge
  request with the project as a source_project
- `create_merge_request_in` indicates a user can create a merge
  request with the project as a target_project
2018-04-11 10:51:15 +02:00
..
conflicts Cache `#can_be_resolved_in_ui?` git operations 2018-03-08 11:54:21 -03:00
add_todo_when_build_fails_service.rb
assign_issues_service.rb
base_service.rb Allow a user to select `allow maintainer to push` 2018-03-07 15:12:31 +01:00
build_service.rb Allow a user to select `allow maintainer to push` 2018-03-07 15:12:31 +01:00
close_service.rb
create_from_issue_service.rb Set target_branch to the ref branch when creating MR from issue 2018-01-17 07:35:23 +01:00
create_service.rb Rename `create_merge_request` permissions 2018-04-11 10:51:15 +02:00
ff_merge_service.rb
get_urls_service.rb
merge_request_diff_cache_service.rb Only cache highlight results for latest MR diffs 2018-03-15 11:49:53 +00:00
merge_service.rb
merge_when_pipeline_succeeds_service.rb
post_merge_service.rb
rebase_service.rb Store only generic message if rebase fails 2018-01-09 17:04:28 +01:00
refresh_service.rb Send notification emails when push to a merge request 2018-03-26 13:24:52 +01:00
reopen_service.rb
resolved_discussion_notification_service.rb
update_service.rb /wip slash command on MR creation 2018-03-01 11:19:14 -03:00
working_copy_base_service.rb Backport 'Rebase' feature from EE to CE 2018-01-05 09:34:59 +01:00