Jan Provaznik b39b5524f2 Use message body for merge request description ... When a merge request is created from email, use message body as merge request description. If message body is empty then merge request description is still created from the source branch commit (if there is only single commit in the merge request). If message body is empty and there are multiple commits in the source branch, then merge request description is left empty. Closes #40968		2017-12-11 11:46:21 +01:00
..
api	Allow git pull/push on project redirects	2017-12-08 17:42:43 +00:00
assets
backup	Remove Rugged::Repository#empty?	2017-12-07 15:33:30 +00:00
banzai	Merge branch 'jprovazn-ignore-anchors' into 'master'	2017-12-08 14:20:31 +00:00
bitbucket
constraints
container_registry
declarative_policy
generators/rails/post_deployment_migration
gitlab	Use message body for merge request description	2017-12-11 11:46:21 +01:00
google_api	Refactor GCP Client#user_agent_header to use #tap	2017-12-04 13:43:45 +01:00
haml_lint
json_web_token
mattermost
microsoft_teams
omni_auth/strategies
peek
rouge/formatters
rspec_flaky
support
system_check
tasks	Merge branch 'hashed-storage-attachments-migration-path' into 'master'	2017-11-28 12:46:39 +00:00
additional_email_headers_interceptor.rb
after_commit_queue.rb	Consistently schedule Sidekiq jobs	2017-12-05 11:59:39 +01:00
banzai.rb
declarative_policy.rb
disable_email_interceptor.rb
email_template_interceptor.rb
event_filter.rb
expand_variables.rb
extracts_path.rb
feature.rb
file_size_validator.rb
gitlab.rb
gt_one_coercion.rb
milestone_array.rb
repository_cache.rb
static_model.rb
system_check.rb
unfold_form.rb
uploaded_file.rb
version_check.rb