d973872072
When an error occurs during merge, the error message is exposed to user and it is also saved in DB. This error message may be user unfriendly (as in !41820) and it could also expose a detailed backend information. Instead of displaying the specific error message, only sanitized generic message is displayed. This is potentially controversial change because disadvantage is that user doesn't get specific reason of failure. Additional changes: * repository.merge including exceptions is is extracted into a separate method to make things clearer * update! is used instead of update so we don't silently ignore an error Related to !41857 |
||
|---|---|---|
| .. | ||
| conflicts | ||
| add_todo_when_build_fails_service_spec.rb | ||
| assign_issues_service_spec.rb | ||
| build_service_spec.rb | ||
| close_service_spec.rb | ||
| create_from_issue_service_spec.rb | ||
| create_service_spec.rb | ||
| ff_merge_service_spec.rb | ||
| get_urls_service_spec.rb | ||
| merge_request_diff_cache_service_spec.rb | ||
| merge_service_spec.rb | ||
| merge_when_pipeline_succeeds_service_spec.rb | ||
| post_merge_service_spec.rb | ||
| rebase_service_spec.rb | ||
| refresh_service_spec.rb | ||
| reopen_service_spec.rb | ||
| resolved_discussion_notification_service_spec.rb | ||
| update_service_spec.rb | ||