In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

.block

.block-content

%h2.block-title Our Standards

:markdown

Examples of behavior that contributes to creating a positive environment include:

1. Using welcoming and inclusive language.

1. Being respectful of differing viewpoints and experiences.

1. Gracefully accepting constructive criticism.

1. Focusing on what is best for the community.

1. Showing empathy towards other community members.

Examples of unacceptable behavior by participants include:

1. The use of sexualized language or imagery and unwelcome sexual attention or advances.

1. Trolling, insulting/derogatory comments, and personal or political attacks.

1. Public or private harassment.

1. Publishing others' private information, such as a physical or electronic address, without explicit permission.

1. Other conduct which could reasonably be considered inappropriate in a professional setting.

.block

.block-content

%h2.block-title Our Responsibilities

:markdown

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

.block

.block-content

%h2.block-title Scope

:markdown

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

.block

.block-content

%h2.block-title Enforcement

:markdown

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at `conduct@gitlab.com`. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

.block

.block-content

%h2.block-title Attribution

:markdown

This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>.

description: "Learn about contributing to GitLab and read the guidelines, contribution process, sponsor the development of new features, and more."

suppress_header: true

extra_css:

-contributing.css

---

.wrapper

.simple-header

%h1 Contribute to GitLab

%p

:markdown

Stay tuned for the next GitLab Hackathon on November 14-15!

#content

.wrapper.container.contributing-content{role: "main"}

.block

.block-content

%h2.block-title Introduction

:markdown

We want to make it as easy as possible for GitLab users to become GitLab contributors, so we’ve created this guide to help you get started. We have multiple tracks to cater to people of varying experience levels.

If you’re uncomfortable getting into open source development right away, you may want to consider the Documentation or Translation tracks. Documentation and Translation are both just as important as code, and we'd be happy to have your contributions.

We want to create a welcoming environment for everyone who is interested in contributing. Please visit our [Code of Conduct page](/community/contribute/code-of-conduct/) to learn more about our committment to an open and welcoming environment.

.block

.block-content

%h2.block-title Development

:markdown

These instructions are for development of GitLab Community Edition specifically. Please note that use of the GitLab Development Kit is currently experimental on Windows. macOS or Linux are recommended for the best contribution experience.

1. Download and set up the [GitLab Development Kit](https://gitlab.com/gitlab-org/gitlab-development-kit), see the [GDK README](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/README.md) for instructions on setting it up and [Troubleshooting](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/troubleshooting.md) if you get stuck.

- Be sure to comment and verify no one else is working on the issue, and to make sure we’re still interested in a given contribution.

- You may also want to comment and ask for help if you’re new or if you get stuck. We’re more than happy to help!

1. Add the feature or fix the bug you’ve chosen to work on.

1. If it's a feature change that impacts users or admins, [update the documentation](https://docs.gitlab.com/ee/development/documentation/).

1. Open a merge request to merge your code and its documentation. The earlier you open a merge request, the sooner you can get feedback. You can mark it as a Work in Progress to signal that you’re not done yet. If you're including documentation changes or need help with documentation, mention `@gl/-docsteam`.

1. Add tests if needed, as well as [a changelog entry](https://docs.gitlab.com/ee/development/changelog.html).

1. Make sure the test suite is passing.

1. Wait for a reviewer. You’ll likely need to change some things once the reviewer has completed a code review for your merge request. You may also need multiple reviews depending on the size of the change.

1. Get your changes merged!

For more information, please see the [Developer Documentation](https://docs.gitlab.com/ee/development/README.html).

.block

.block-content

%h2.block-title Documentation

:markdown

This section pertains to documentation changes that are independent of other code/feature changes. For documentation changes that accompany changes to code/features, see the Development section above.

See the [Documentation Styleguide](https://docs.gitlab.com/ee/development/documentation/styleguide.html) and [Writing Documentation](https://docs.gitlab.com/ee/development/documentation/) pages for more important details on writing documentation for GitLab.

1. Find a page that’s lacking important information or that has a spelling/grammar mistake.

1. Click the "Edit this page" link at the bottom of the page, fork the relevant project, and modify the documentation in GitLab’s web editor. Alternatively, you can fork the relevant project locally and edit the corresponding file(s) in its `/doc` or `/docs` path.

1. Open a merge request and remember to follow [branch naming conventions](https://docs.gitlab.com/ee/development/writing_documentation.html#branch-naming) and append `-docs` to the name of the branch.

1. Mention `@gl/-docsteam` in a comment, then wait for a review. You may need to change things if a reviewer requests it.

1. Get your changes merged!

For those interested in writing full technical articles, we also have a [GitLab Community Writers Program](/community-writers/) which includes compensation.

.block

.block-content

%h2.block-title Translation

:markdown

Please note that GitLab is in the process of being internationalized. Not all pages have been updated to be translatable, and all languages other than English are incomplete. For more information visit [the documentation](https://docs.gitlab.com/ee/development/i18n/translation.html).

1. Improve existing translations, vote on new translations, and/or contribute new translations to your given language.

1. Once approved, your changes will automatically be included in the next version of GitLab!

.block

.block-content

%h2.block-title UX Design

:markdown

These instructions are for those wanting to contribute UX designs specifically. The UX department at GitLab uses Sketch for all of its designs. See the [Design Repository documentation](https://gitlab.com/gitlab-org/gitlab-design/blob/master/README.md#getting-started) for details on working with our files. Visit our [Contributing guidelines](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/index.md) to read our general guidelines for contributing. While they are code-focused instructions, they will help you understand the overall process of contributing.

1. If you want to leverage our existing design library to submit UX proposals, you can download our pattern library Sketch file following the instructions in the [Design Repository documentation](https://gitlab.com/gitlab-org/gitlab-design/blob/master/README.md#getting-started).

1. You do not need to use our Sketch files to contribute. We will gladly accept hand-made drawings and sketches, wireframes, manipulated DOM screenshots, prototypes, etc.

1. You can find documentation on our design patterns in our [Design System](https://design.gitlab.com/). Use it to understand where and when to use common design solutions.

1. If you don't already have an idea for a UX improvement, you can pick an existing problem to work on from [this list of issues looking for community contributions](https://gitlab.com/groups/gitlab-org/-/issues?state=opened&label_name[]=Accepting+merge+requests&label_name[]=UX&assignee_id=0&sort=weight)

1. Be sure to comment and verify no one else is working on the UX for the issue, and to make sure we’re still interested in a given contribution.

1. Ask questions to clarify the problem being solved and make your UX suggestions using words, low-fi wireframes, hi-fi designs, or even prototypes. Ask for help if you’re new or if you get stuck. We’re happy to help! You can ping the UX Department in an issue or comment using this handle `@gitlab-com/gitlab-ux`.

1. Ask for a review from a GitLab UX Designer. You’ll likely need to change some things once the reviewer has completed their review. You may also require multiple reviews depending on the scope of the UX.

1. Get your UX approved!

.block

.block-content

%h2.block-title Getting Help

:markdown

If you need help while contributing to GitLab, below are some of the resources that are available.

1. Get in touch with [Merge Request Coaches](https://about.gitlab.com/job-families/merge-request-coach/). To find a merge request coach, go to the [GitLab Team Page](https://about.gitlab.com/team/) and search for "merge request coach".

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

.block

.block-content

%h2.block-title Our Standards

:markdown

Examples of behavior that contributes to creating a positive environment include:

1. Using welcoming and inclusive language.

1. Being respectful of differing viewpoints and experiences.

1. Gracefully accepting constructive criticism.

1. Focusing on what is best for the community.

1. Showing empathy towards other community members.

Examples of unacceptable behavior by participants include:

1. The use of sexualized language or imagery and unwelcome sexual attention or advances.

1. Trolling, insulting/derogatory comments, and personal or political attacks.

1. Public or private harassment.

1. Publishing others' private information, such as a physical or electronic address, without explicit permission.

1. Other conduct which could reasonably be considered inappropriate in a professional setting.

.block

.block-content

%h2.block-title Our Responsibilities

:markdown

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

-path=current_page.data.cannonical_path

.block

.block-content

%h2.block-title Scope

:markdown

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

%p{:style=>"text-align: center; margin-top: 30px;"}

Redirecting to

%a{href: "#{path}"} https://about.gitlab.com#{path}

.block

.block-content

%h2.block-title Enforcement

:markdown

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at `conduct@gitlab.com`. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

.block

.block-content

%h2.block-title Attribution

:markdown

This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>.

description: "Learn about contributing to GitLab and read the guidelines, contribution process, sponsor the development of new features, and more."

suppress_header: true

extra_css:

-contributing.css

layout: blank

title: Redirecting

cannonical_path: "/community/contribute/"

---

.wrapper

.simple-header

%h1 Contributing to GitLab

%p

:markdown

Stay tuned for the next GitLab Hackathon on November 14-15!

#content

.wrapper.container.contributing-content{role: "main"}

.block

.block-content

%h2.block-title Introduction

:markdown

We want to make it as easy as possible for GitLab users to become GitLab contributors, so we’ve created this guide to help you get started. We have multiple tracks to cater to people of varying experience levels.

If you’re uncomfortable getting into open source development right away, you may want to consider the Documentation or Translation tracks. Documentation and Translation are both just as important as code, and we'd be happy to have your contributions.

-path=current_page.data.cannonical_path

We want to create a welcoming environment for everyone who is interested in contributing. Please visit our [Code of Conduct page](https://about.gitlab.com/contributing/code-of-conduct) to learn more about our committment to an open and welcoming environment.

%p{:style=>"text-align: center; margin-top: 30px;"}

Redirecting to

%a{href: "#{path}"} https://about.gitlab.com#{path}

.block

.block-content

%h2.block-title Development

:markdown

These instructions are for development of GitLab Community Edition specifically. Please note that use of the GitLab Development Kit is currently experimental on Windows. macOS or Linux are recommended for the best contribution experience.

1. Download and set up the [GitLab Development Kit](https://gitlab.com/gitlab-org/gitlab-development-kit), see the [GDK README](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/README.md) for instructions on setting it up and [Troubleshooting](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/troubleshooting.md) if you get stuck.

- Be sure to comment and verify no one else is working on the issue, and to make sure we’re still interested in a given contribution.

- You may also want to comment and ask for help if you’re new or if you get stuck. We’re more than happy to help!

1. Add the feature or fix the bug you’ve chosen to work on.

1. If it's a feature change that impacts users or admins, [update the documentation](https://docs.gitlab.com/ee/development/documentation/).

1. Open a merge request to merge your code and its documentation. The earlier you open a merge request, the sooner you can get feedback. You can mark it as a Work in Progress to signal that you’re not done yet. If you're including documentation changes or need help with documentation, mention `@gl/-docsteam`.

1. Add tests if needed, as well as [a changelog entry](https://docs.gitlab.com/ee/development/changelog.html).

1. Make sure the test suite is passing.

1. Wait for a reviewer. You’ll likely need to change some things once the reviewer has completed a code review for your merge request. You may also need multiple reviews depending on the size of the change.

1. Get your changes merged!

For more information, please see the [Developer Documentation](https://docs.gitlab.com/ee/development/README.html).

.block

.block-content

%h2.block-title Documentation

:markdown

This section pertains to documentation changes that are independent of other code/feature changes. For documentation changes that accompany changes to code/features, see the Development section above.

See the [Documentation Styleguide](https://docs.gitlab.com/ee/development/documentation/styleguide.html) and [Writing Documentation](https://docs.gitlab.com/ee/development/documentation/) pages for more important details on writing documentation for GitLab.

1. Find a page that’s lacking important information or that has a spelling/grammar mistake.

1. Click the "Edit this page" link at the bottom of the page, fork the relevant project, and modify the documentation in GitLab’s web editor. Alternatively, you can fork the relevant project locally and edit the corresponding file(s) in its `/doc` or `/docs` path.

1. Open a merge request and remember to follow [branch naming conventions](https://docs.gitlab.com/ee/development/writing_documentation.html#branch-naming) and append `-docs` to the name of the branch.

1. Mention `@gl/-docsteam` in a comment, then wait for a review. You may need to change things if a reviewer requests it.

1. Get your changes merged!

For those interested in writing full technical articles, we also have a [GitLab Community Writers Program](/community-writers/) which includes compensation.

.block

.block-content

%h2.block-title Translation

:markdown

Please note that GitLab is in the process of being internationalized. Not all pages have been updated to be translatable, and all languages other than English are incomplete. For more information visit [the documentation](https://docs.gitlab.com/ee/development/i18n/translation.html).

1. Improve existing translations, vote on new translations, and/or contribute new translations to your given language.

1. Once approved, your changes will automatically be included in the next version of GitLab!

.block

.block-content

%h2.block-title UX Design

:markdown

These instructions are for those wanting to contribute UX designs specifically. The UX department at GitLab uses Sketch for all of its designs. See the [Design Repository documentation](https://gitlab.com/gitlab-org/gitlab-design/blob/master/README.md#getting-started) for details on working with our files. Visit our [Contributing guidelines](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/index.md) to read our general guidelines for contributing. While they are code-focused instructions, they will help you understand the overall process of contributing.

1. If you want to leverage our existing design library to submit UX proposals, you can download our pattern library Sketch file following the instructions in the [Design Repository documentation](https://gitlab.com/gitlab-org/gitlab-design/blob/master/README.md#getting-started).

1. You do not need to use our Sketch files to contribute. We will gladly accept hand-made drawings and sketches, wireframes, manipulated DOM screenshots, prototypes, etc.

1. You can find documentation on our design patterns in our [Design System](https://design.gitlab.com/). Use it to understand where and when to use common design solutions.

1. If you don't already have an idea for a UX improvement, you can pick an existing problem to work on from [this list of issues looking for community contributions](https://gitlab.com/groups/gitlab-org/-/issues?state=opened&label_name[]=Accepting+merge+requests&label_name[]=UX&assignee_id=0&sort=weight)

1. Be sure to comment and verify no one else is working on the UX for the issue, and to make sure we’re still interested in a given contribution.

1. Ask questions to clarify the problem being solved and make your UX suggestions using words, low-fi wireframes, hi-fi designs, or even prototypes. Ask for help if you’re new or if you get stuck. We’re happy to help! You can ping the UX Department in an issue or comment using this handle `@gitlab-com/gitlab-ux`.

1. Ask for a review from a GitLab UX Designer. You’ll likely need to change some things once the reviewer has completed their review. You may also require multiple reviews depending on the scope of the UX.

1. Get your UX approved!

.block

.block-content

%h2.block-title Getting Help

:markdown

If you need help while contributing to GitLab, below are some of the resources that are available.

1. Get in touch with [Merge Request Coaches](https://about.gitlab.com/job-families/merge-request-coach/). To find a merge request coach, go to the [GitLab Team Page](https://about.gitlab.com/team/) and search for "merge request coach".