TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Community Growth and Contribution Milestones

5 posts · Jul 2022 – Sep 2026

What this trail covers

GitLab has improved its open source community growth and contribution milestones by developing and implementing a semi-automated onboarding solution. This solution leverages GitLab's own tools, including issue templates, scheduled pipelines, webhooks, GLQL, and project mirroring, to streamline the contributor journey. Key enhancements include personalized onboarding issues, standardized responses via comment templates, immediate pipeline triggers for access requests, automated nudges, and the integration of new features like Scala language support for Orbit and GitLab Duo, instance-level enforcement for Secret Push Protection, configurable merge train pipeline limits, supported-platform details for container image indexes, and improved screen reader context for documentation pages. The platform also introduced new predefined variables (`CI_TRACEPARENT`, `CI_TRACESTATE`) for W3C Trace Context in CI/CD jobs, enabling better correlation across pipelines and distributed systems. The User Applications REST API and Token Information API have been enhanced for programmatic management of OAuth applications and SCIM tokens, respectively, improving automation around token inventory and governance.

All GitLab trails
  1. Co-Create: Building GitLab with our usersThis post details how user contributions through the Co-Create program have led to specific product improvements. These include: adding Scala language support to GitLab Orbit for GitLab Duo context, enabling instance-level enforcement for Secret Push Protection, implementing configurable merge train pipeline limits, showing supported platforms for multi-architecture container images, and providing more context for screen reader users on documentation pages. It also highlights the addition of `CI_TRACEPARENT` and `CI_TRACESTATE` predefined variables for W3C Trace Context in CI/CD jobs, the enhancement of the User Applications REST API for programmatic management of OAuth applications, and the addition of SCIM token support to the Token Information API. These contributions represent direct product enhancements driven by user needs and collaboration.
  2. Pursuing faster time-to-merge for wider community contributionsIntroduced workflow labels (`workflow::ready for review`, `workflow::in dev`, `workflow::blocked`) to provide clearer states for merge requests, allowing community contributors to self-manage their MRs. Implemented automation via `@gitlab-bot ready` to set the state and assign reviewers. This has reduced the median time MRs spend in the 'ready for review' state from 17 days to 5 days and increased the median Open Community MR Age (OCMA) from 139 days to 78 days. Future work includes automating the transition of MRs back to `workflow::in dev` when further changes are needed.
  3. How to quickly (and successfully) onboard engineersThis post details GitLab's approach to onboarding new software engineers, focusing on accelerating their integration and value creation. It outlines a structured process that begins before day one, emphasizing the use of an 'onboarding issue' as a single source of truth. Key elements include assigning an onboarding buddy, encouraging pair programming, facilitating 'coffee chats' for networking, tailoring the experience to individual roles, and aiming for engineers to ship production code within a week. The post highlights the importance of communication, psychological safety, and demonstrating GitLab's CREDIT values throughout the onboarding journey.