Add MR Rate Tips

Why is this change being made?

In an effort to improve our KPIs, I am documenting some of the best practices we have been talking about as a team around MR Rate and Mean time to Merge (MTTM). These are things we are experimenting with for now, which I called out in this MR. We can also use this information to see how these tips impact our MR rate and MTTM and ensure the team is using these best practices.

I only included a small set of tips as a starting point. We could add more as we find them effective.

Review App: https://mnohr-apm-mr-rate.about.gitlab-review.app/handbook/engineering/development/ops/monitor/apm/index.html#merge-request-rate-kpi

Handbook: https://about.gitlab.com/handbook/engineering/development/ops/monitor/apm/index.html#merge-request-rate-kpi

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
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • 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 relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack