We want to make it as easy as possible for GitLab users to become GitLab contributors, so we’ve created this contribution guide to help you get started. We have multiple tracks to cater to people of varying interests so that everyone can contribute.
In addition to Open Source Development, there are also Documentation, Translation, and UX Design tracks. Documentation, Translation, and UX Design are all just as important as code, and we'd be happy to welcome your contributions. You can see the wider community contribution data in our community dashboard.
We want to create a welcoming environment for everyone who is interested in contributing. Please visit our Code of Conduct page to learn more about our commitment to an open and welcoming environment.
Whether it's fixing bugs, adding new features, helping with reviews, GitLab is a great Open Source community for developers from all backgrounds. Many contributors actually started contributing to GitLab development without being familiar with languages like Ruby.More on Contributing to Development
Contributing to documentation is a great way to get familiar with the GitLab development process and to meet reviewers and other community members. From fixing typos to better organizing our documentation, you will find many areas where you can contribute.More on Contributing to Documentation
GitLab is being translated into more than 35 languages, and this is also driven by wider community members. If you speak another language, you can join more than 1,500 community members who are helping translate GitLab. Come and help us speak your language!More on Contributing to Translation
To help make our product easy to use and built for a diverse group of people, we welcome contributions from the wider community. You can help us better understand your needs and how you use GitLab, or make your own contribution and GitLab UX team members will assist, as needed.More on Contributing to UX Design
If you need any help while contributing to GitLab, below are some of the resources that are available.
- Ask questions on the Contributors Gitter Channel.
- Get in touch with Merge Request Coaches. To find a merge request coach, go to the GitLab Team Page and search for "merge request coach". You can also mention Merge Request Coaches by typing
@gitlab-org/coachesin a comment.
- Find reviewers & maintainers of Gitlab projects in our handbook and mention them in a comment.
- If you have feature ideas/questions, you can search for existing issues or create a new issue if there isn't one already. Feel free to mention product team members in the issue.
- For any other questions or feedback, please email