Recognize Your Team with GitLab Achievements
The new way to make team contributions visible.
1What Are GitLab Achievements?
GitLab Achievements are custom digital badges created to recognize outstanding team contributions. Each badge includes a name, description, and avatar. Examples include 'First Merged MR', 'Certified', or 'Contributor of the Month'. Badges appear on the recipient's profile alongside their contribution history. Available since GitLab 19.2 across all plans (Free, Premium, Ultimate) and deployment models (GitLab.com, Self-Managed, Dedicated).
2How It Works
Achievements work in two stages: First, a reusable template is created at group level. Then this badge is awarded to specific individuals with an optional personal message. Messages support GitLab Flavored Markdown, allowing direct links to relevant merge requests, issues, or events. Recipients maintain control - a badge won't appear on anyone's profile until accepted via email notification link. This ensures recognition is never forced.
3For Internal Engineering Teams
Most teams will use badges to recognize internal engineering achievements. They're ideal for making typically unnoticed efforts visible - rewarding fastest reviewers, certified engineers, incident responders, or guild members. For example, engineers completing onboarding might receive a 'Certified' badge. Such recognition shows the whole organization who keeps the wheels turning.
4Value for Open Source Communities
GitLab specifically developed this feature for open source contributors. For unpaid contributors, visible recognition is often the only reward. 'First Contribution' badges can be awarded automatically, or 'Notable Contributor' badges distributed each release. Contributors gain something tangible to showcase, while maintainers get a consistent recognition method. This provides scalable appreciation for community programs.
55 Key Use Cases
1) Identify core contributors - Let your community know who's who. 2) Reward great reviews - Give badges for quick turnarounds and mentoring. 3) Encourage learning - Recognize certification earners or new skill adopters. 4) Celebrate milestones - Mark first contributions, 100th contributions. 5) Run programs - Create special badges for hackathons or quarterly campaigns.
6Technical Implementation
Achievements are scriptable via GraphQL API. For example, automatically award 'First Contribution' when someone's initial merge request merges. Badges come in three types: 1) Awarded once and permanent ('First Merged MR'), 2) Awarded once but revocable ('Core Team Member'), 3) Repeatable ('Contributor of the Month'). Personal messages add particular value for recurring awards, linking to specific achievements.
7A Community-Built Feature
This feature originated not from the core product team but from the 'Co-create and Community Engineering' team and wider community, documented in Epic #9429. Interestingly, a feature for recognizing contributors was itself community-created. This embodies GitLab's open participation philosophy - the 'everyone can contribute' value in action.
8Why It Matters
Recognition is among the most cost-effective tools for retention, motivation, and belonging. A profile badge takes a minute to award but provides lasting value. 'Team' can mean your company, open source project, or broader community. The value depends entirely on who you're recognizing and what behaviors you want to reinforce. GitLab Achievements make this recognition structured and scalable.
Original article: GitLab — GitLab Başarı Rozetleri ile Takımınızı Tanıyın