Skip to content

Migrating the default merge request template from project settings into...

Ian Pedowitz requested to merge ipedowitz-master-patch-43955 into master

Why is this change being made?

In discussion with @marshall007, we discovered that the default merge request template is hosted in the projects settings rather than .gitlab/merge_request_templates/Default.md. This meant that only Maintainers can edit the default template.

In the spirit of everyone can contribute, migrating the content to .gitlab/merge_request_templates/Default.md and then @marshall007 will remove this from the projects settings.

In addition to migrating the template, I've made the following other changes:

  1. Tweaked some wording
  2. Defined MR's first use in the checklist
  3. Linked to say-why-not-just-what directly
  4. Spelled out the first use of DRI and linked to the definition of DRI

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Ian Pedowitz

Merge request reports