The Fast-Track Playbook to Becoming a GitLab Core Contributor

Description and use

A step‑by‑step guide that helps newcomers efficiently locate suitable issues, set up a lightweight development environment, pass CI gates on the first try, and earn recognition through GitLab’s Contributor Platform.

Problem

New contributors feel overwhelmed by GitLab’s large codebase and complex contribution process.

Outcome

Following the playbook enables a first‑time contributor to submit a merged Merge Request quickly and gain points on the Contributor Platform.

Workflow

• Filter issues by labels "quick win" and "community contribution" and state "opened"
• Comment on the issue asking for assignment
• Fork the repository and create a feature branch
• Write the fix and unit tests
• Run local linters (rubocop, ruff, markdownlint)
• Open a Merge Request with a clear description and "Closes #XYZ"
• Address review feedback
• Celebrate merge and share learning

Evidence

GitLab uses a disciplined issue labeling system. To find issues designed specifically for community members with active maintainer mentorship, filter by these exact labels:

Source

For quick documentation, frontend, or minor backend adjustments, open any repository in Gitpod or a GitLab Web IDE workspace. The dependencies and environment are pre-provisioned in the cloud.

Source

Run local linters (rubocop, ruff, or markdownlint).

Source

GitLab uses GitLab Duo Code Review and Reviewer Roulette to assign your MR to a coach or maintainer.

Source