-
Mitchell Nielsen authored
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).
Mitchell Nielsen authoredRenames '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).
Deprecated Configuration.md 1.96 KiB
What does this MR do?
Related issues
Deprecation schedule
Configuration Key | Deprecation Date | Removal Date |
---|---|---|
TBD | TBD | TBD |
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 the dev.gitlab.org mirror for this branch if the change is touching anything besides documentation or internal cookbooks. Please note that feature branches are not automatically mirrored to dev.gitlab.org, and should be manually pushed whenever necessary.
-
trigger-package
has a green pipeline running against latest commit - When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow
Expected (please provide an explanation if not completing)
- Test plan indicating conditions for success has been posted and passes
- Documentation created/updated
- Tests updated
- Equivalent MR/issue for the GitLab Chart opened
- Notify Product for inclusion in release notes