Thank you for your interest in contributing to GitLab. This guide details how contribute to GitLab in a way that is efficient for everyone. If you have read this guide and want to know how the GitLab core-team operates please see the GitLab contributing process.
By submitting code as an individual you agree to the individual contributor license agreement. By submitting code as an entity you agree to the corporate contributor license agreement.
Please report suspected security vulnerabilities in private to [email protected], also see the disclosure section on the GitLab.com website. Please do NOT create publicly viewable issues for suspected security vulnerabilities.
GitLab is a popular open source project and the capacity to deal with issues and merge requests is limited. Out of respect for our volunteers, issues and merge requests not in line with the guidelines listed in this document may be closed without notice.
Please treat our volunteers with courtesy and respect, it will go a long way towards getting your issue resolved.
Issues and merge requests should be in English and contain appropriate language for audiences of all ages.
Please help other GitLab users when you can. The channnels people will reach out on can be found on the getting help page. Sign up for the mailinglist, answer GitLab questions on StackOverflow or respond in the irc channel. You can also sign up on CodeTriage to help with one issue every day.
To get support for your particular problem please use the getting help channels.
The GitLab CE issue tracker on GitLab.com is only for obvious errors in the latest stable or development release of GitLab. If something is wrong but it is not a regression compared to older versions of GitLab please do not open an issue but a feature request. When submitting an issue please conform to the issue submission guidelines listed below. Not all issues will be addressed and your issue is more likely to be addressed if you submit a merge request which partially or fully addresses the issue.
Do not use the issue tracker for feature requests. We have a specific feature request forum for this purpose. Please keep feature requests as small and simple as possible, complex ones might be edited to make them small and simple.
Please send a merge request with a tested solution or a merge request with a failing test instead of opening an issue if you can. If you're unsure where to post, post to the mailing list or Stack Overflow first. There are a lot of helpful GitLab users there who may be able to help you quickly. If your particular issue turns out to be a bug, it will find its way from there.
Search the issues for similar entries before submitting your own, there's a good chance somebody else had the same issue. Show your support with :+1: and/or join the discussion. Please submit issues in the following format (as the first post):
- Summary: Summarize your issue in one sentence (what goes wrong, what did you expect to happen)
- Steps to reproduce: How can we reproduce the issue
- Expected behavior: Describe your issue in detail
- Observed behavior
- Relevant logs and/or screenshots: Please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.
- Output of checks
- Results of GitLab Application Check (
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true); we will only investigate if the tests are passing - Version of GitLab you are running; we will only investigate issues in the latest stable and development releases as per the maintenance policy
- Add the last commit SHA-1 of the GitLab version you used to replicate the issue (obtainable from the help page)
- Describe your setup (use relevant parts from
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)
- Results of GitLab Application Check (
- Possible fixes: If you can, link to the line of code that might be responsible for the problem
We welcome merge requests with fixes and improvements to GitLab code, tests, and/or documentation. The features we would really like a merge request for are listed with the status 'accepting merge requests' on our feature request forum but other improvements are also welcome. If you want to add a new feature that is not marked it is best to first create a feedback issue (if there isn't one already) and leave a comment asking for it to be marked accepting merge requests. Please include screenshots or wireframes if the feature will also change the UI.
Merge requests can be filed either at gitlab.com or github.com.
If you are new to GitLab development (or web development in general), search for the label easyfix (gitlab.com, github). Those are issues easy to fix, marked by the GitLab core-team. If you are unsure how to proceed but want to help, mention one of the core-team members to give you a hint.
To start with GitLab download the GitLab Development Kit and see Development section in the help file.
If you can, please submit a merge request with the fix or improvements including tests. If you don't know how to fix the issue but can write a test that exposes the issue we will accept that as well. In general bug fixes that include a regression test are merged quickly while new features without proper tests are least likely to receive timely feedback. The workflow to make a merge request is as follows:
- Fork the project into your personal space on GitLab.com
- Create a feature branch
- Write tests and code
- Add your changes to the CHANGELOG
- If you are changing the README, some documentation or other things which have no effect on the tests, add
[ci skip]somewhere in the commit message - If you have multiple commits please combine them into one commit by squashing them
- Push the commit to your fork
- Submit a merge request (MR) to the master branch
- The MR title should describe the change you want to make
- The MR description should give a motive for your change and the method you used to achieve it
- If the MR changes the UI it should include before and after screenshots
- If the MR changes CSS classes please include the list of affected pages
grep css-class ./app -R - Link relevant issues and/or feature requests from the merge request description and leave a comment on them with a link back to the MR
- Be prepared to answer questions and incorporate feedback even if requests for this arrive weeks or months after your MR submission
- If your MR touches code that executes shell commands, make sure it adheres to the shell command guidelines.
- Also have a look at the shell command guidelines if your code reads or opens files, or handles paths to files on disk.
The official merge window is in the beginning of the month from the 1st to the 7th day of the month. The best time to submit a MR and get feedback fast. Before this time the GitLab B.V. team is still dealing with work that is created by the monthly release such as regressions requiring patch releases. After the 7th it is already getting closer to the release date of the next version. This means there is less time to fix the issues created by merging large new features.
Please keep the change in a single MR as small as possible. If you want to contribute a large feature think very hard what the minimum viable change is. Can you split functionality? Can you only submit the backend/API code? Can you start with a very simple UI? Can you do part of the refactor? The increased reviewability of small MR's that leads to higher code quality is more important to us than having a minimal commit log. The smaller a MR is the more likely it is it will be merged (quickly), after that you can send more MR's to enhance it.
For examples of feedback on merge requests please look at already closed merge requests. If you would like quick feedback on your merge request feel free to mention one of the Merge Marshalls of the core-team. Please ensure that your merge request meets the contribution acceptance criteria.
If you contribute to GitLab please know that changes involve more than just code. We have the following definition of done. Please ensure you support the feature you contribute through all of these steps.
- Description explaning the relevancy (see following item)
- Working and clean code that is commented where needed
- Unit and integration tests that pass on the CI server
- Documented in the /doc directory
- Changelog entry added
- Reviewed and any concerns are addressed
- Merged by the project lead
- Added to the release blog article
- Added to the website if relevant
- Community questions answered
- Answers to questions radiated (in docs/wiki/etc.)
If you add a dependency in GitLab (such as an operating system package) please consider updating the following and note the applicability of each in your merge request:
- Note the addition in the release blog post (create one if it doesn't exist yet) https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/
- Upgrade guide, for example https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/7.5-to-7.6.md
- Upgrader https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/upgrader.md#2-run-gitlab-upgrade-tool
- Installation guide https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md#1-packages-dependencies
- GitLab Development Kit https://gitlab.com/gitlab-org/gitlab-development-kit
- Test suite https://gitlab.com/gitlab-org/gitlab-ci/blob/master/doc/examples/configure_a_runner_to_run_the_gitlab_ce_test_suite.md
- Omnibus package creator https://gitlab.com/gitlab-org/omnibus-gitlab
- What does this MR do?
- Are there points in the code the reviewer needs to double check?
- Why was this MR needed?
- What are the relevant issue numbers / Feature requests?
- Screenshots (if relevant)
- The change is as small as possible (see the above paragraph for details)
- Include proper tests and make all tests pass (unless it contains a test exposing a bug in existing code)
- All tests have to pass, if you suspect a failing CI build is unrelated to your contribution ask for tests to be restarted. See the CI setup document on who you can ask for test restart.
- Initially contains a single commit (please use
git rebase -ito squash commits) - Can merge without problems (if not please merge
master, never rebase commits pushed to the remote server) - Does not break any existing functionality
- Fixes one specific issue or implements one specific feature (do not combine things, send separate merge requests if needed)
- Migrations should do only one thing (eg: either create a table, move data to a new table or remove an old table) to aid retrying on failure
- Keeps the GitLab code base clean and well structured
- Contains functionality we think other users will benefit from too
- Doesn't add configuration options since they complicate future changes
- Changes after submitting the merge request should be in separate commits (no squashing). You will be asked to squash when the review is over, before merging.
- It conforms to the following style guides. If your change touches a line that does not follow the style, modify the entire line to follow it. This prevents linting tools from generating warnings. Don't touch neighbouring lines. As an exception, automatic mass refactoring modifications may leave style non-compliant.
- Ruby.
Important sections include Source Code Layout
and Naming. Use:
- multi-line method chaining style Option B: dot
.on previous line - string literal quoting style Option A: single quoted by default
- multi-line method chaining style Option B: dot
- Rails
- Testing
- CoffeeScript
- Shell commands created by GitLab contributors to enhance security
- Markdown
- Database Migrations
- Documentation styleguide
- Interface text should be written subjectively instead of objectively. It should be the gitlab core team addressing a person. It should be written in present time and never use past tense (has been/was). For example instead of "prohibited this user from being saved due to the following errors:" the text should be "sorry, we could not create your account because:". Also these excellent writing guidelines.
This is also the style used by linting tools such as RuboCop, PullReview and Hound CI.
As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or religion.
Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
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. Project maintainers who do not follow the Code of Conduct may be removed from the project team.
This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
Instances of abusive, harassing, or otherwise unacceptable behavior can be reported by emailing [email protected]
This Code of Conduct is adapted from the Contributor Covenant, version 1.1.0, available at http://contributor-covenant.org/version/1/1/0/