Merge Request Coach Lifecycle
Applying to become a Merge Request Coach
- Create a new issue using the
mr_coach_onboarding
template (see screenshot below). - Fill in the placeholders in the issue template with your information.
- Assign the issue to yourself.
- Work through the steps in that new issue.
Stepping down gracefully
If you are no longer able to serve as a Merge Request Coach, you should identify another GitLab team member to take your place so that the capacity of the remaining coaches remains the same. When you are ready to step down, you need to:
- Make an announcement on the
#mr-coaching
Slack channel. - Update the
team.yml
file to remove “Merge Request Coach”. - Remove yourself from the
@gitlab-org/coaches
group.
References/resources
- Merge Request Coach responsibilities
- Merge Request Coach collaboration guidelines
- Community Discord channel: please join if you haven’t already!
Current Merge Request Coaches
GitLab currently has 39 merge request coaches:
Name | Group | Departments |
---|---|---|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
Security Risk Management:Security Policies |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
Software Supply Chain Security:Compliance |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
Core |
|
![]() |
Tenant Scale |
|
![]() |
Monitor:Platform Insights |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
Verify:Runner |
|
![]() |
None |
|
![]() |
Tenant Scale |
|
![]() |
None |
|
![]() |
None |
|
![]() |
Tenant Scale |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
![]() |
Tenant Scale |
|
![]() |
Environments |
|
![]() |
None |
|
![]() |
None |
|
![]() |
None |
|
Last modified January 7, 2025: Move marketing images to static folder (
a54c394b
)