Merge Request Coach

1. You are here:
2. Roles
3. Expert
4. Merge Request Coach

The main goal of a Merge Request Coach is to help merge requests from the community get merged into GitLab.

Responsibilities

• Triage merge requests labeled ~Community Contribution.
• Close merge requests that we don't want, with a clear explanation on the reasons why, so that people don't feel discouraged.
• Help contributors to get their merge requests to meet the contribution acceptance criteria.
• If the contributor is unresponsive or if they are unable to finish it, finish their merge requests.
  1. Close the original merge request and say that you will finish it.
  2. Check out the branch locally.
  3. Keep at least one original commit (you can squash commits if there are a lot) from the author.
  4. Make sure a changelog entry crediting the author exists.
  5. Add your own commits to improve and finish the original work.
  6. Push to a new branch and open a new merge request.
• Make it easy to contribute to GitLab even for people who are new to Ruby, JavaScript, or programming entirely.

Apply

1. Create an MR to add "Merge Request coach" to your team page entry.
2. Explain your motivation in the MR body:
   • Why you want to become a Merge Request coach?
   • How much time you are planning to spend on it?
   • Which duties you are focusing on (e.g. triage, finish stale MRs)?
3. Mention @gitlab-org/coaches and assign one of them.