Use 'General Change.md' as default MR description
What does this MR do?
Follow-up to !6692 (merged).
Use 'General Change.md' as default MR description
Renames 'General Change.md' to 'Default.md' so it is automatically
used as the default merge request description.
Related documentation:
https://docs.gitlab.com/ee/user/project/description_templates.html#supported-variables-in-merge-request-templates
This ensures that the '%{first_multiline_commit}' variable works as
expected, given the note in the documentation:
> This feature is available only for the default template.
The [default template docs](https://docs.gitlab.com/ee/user/project/description_templates.html#set-a-default-template-for-merge-requests-and-issues)
state that the file needs to be named 'Default.md' (case insensitive).
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks -
trigger-package
has a green pipeline running against latest commit -
(after merge) Remove the manually-entered default merge request description under Settings > Merge Requests > Default description template for merge requests
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for the GitLab Chart opened
Edited by Mitchell Nielsen