Docs feedback - feature proposal: Add ability to include `--log` in the `git merge` command on merge of a merge request
Release notes
None
Problem to solve
Currently the default message from GitLab on Merges is the same default as the git merge command. The problem is that for some script and Jira automation we are unable on merges to interrogate the commits messages of the branch in order to capture all the Jira issues that need to be updated automatically. Git provides on git merge the --log option that captures all the relevant commit messages being merged in. As a Merge Request resolver, I want to be able to merge through GitLab and have the message on my merge commit contain the relevant commit messages from what is being merged in instead of just a plain default, so that I can use that information for other processes that update relevant tracking systems accordingly.
Intended users
Developers, Maintainers and Owners of Repositories/Groups
User experience goal
The user should be able to toggle a setting on for Repository or Group and see that merge requests on merge have more than the default merge commit message and includes those that come with the git merge --log command
Proposal
I propose that GitLab offer a new setting at the Group and Repository levels where the parent setting overrides the Child. The setting would be added to General-> Merge Requests -> Merge Options section. The option would say "Should include relevant commits to merge in merge commit message"
If selected the option would add to the git merge command the option --log. If not selected then it would remain as is.