Include fork project's path in merge commits with same source and target branch name
Description
When merge request came from a fork when the source and target repository branch name are the same, weird message commit title.
Example:
Merge branch 'feature/clean-db' into 'feature/clean-db'
Proposal
Would be preferable to include a reference to the forked project's path in the message like:
Merge branch 'dev01:feature/clean-db' into 'feature/clean-db'
Links / references
Documentation blurb
Overview
What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?
Use cases
Who is this for? Provide one or more use cases.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml
Edited by 🤖 GitLab Bot 🤖