Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Contributing to Documentation

Documentation

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 Contributing to Development page.

See the Documentation Styleguide and Writing Documentation pages for more important details on writing documentation for GitLab.

  1. Visit docs.gitlab.com for the latest documentation for GitLab CE/EE, GitLab Runner, and GitLab Omnibus.
  2. Find a page that’s lacking important information or that has a spelling/grammar mistake. NOTE: Gitlab uses US English.
  3. 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.
  4. Open a merge request and remember to follow branch naming conventions.
  5. Mention @gl-docsteam in a comment, then wait for a review. You may need to change things if a reviewer requests it.
  6. Get your changes merged!

For those interested in writing full technical articles, we also have a GitLab Community Writers Program which includes compensation.