Commit 63b78a3989e00b917e51841d4960beca9a11b315
Exists in
master
and in
4 other branches
Merge branch 'move-issue-above-pr' of /home/git/repositories/gitlab/gitlabhq
Showing
1 changed file
with
21 additions
and
21 deletions
Show diff stats
CONTRIBUTING.md
| 1 | 1 | # Contribute to GitLab |
| 2 | 2 | |
| 3 | -This guide details how to use pull requests and the issues to improve GitLab. | |
| 3 | +This guide details how to use issues and pull requests to improve GitLab. | |
| 4 | 4 | |
| 5 | -## Closing policy for pull requests and issues | |
| 5 | +## Closing policy for issues and pull requests | |
| 6 | 6 | |
| 7 | -Pull requests and issues not in line with the guidelines listed in this document will be closed with just a link to this paragraph. GitLab is a popular open source project and the capacity to deal with issues and pull requests is limited. To get support for your problems please use other channels as detailed in [the getting help section of the readme](https://github.com/gitlabhq/gitlabhq#getting-help). Professional [support subscriptions](http://www.gitlab.com/subscription/) and [consulting services](http://www.gitlab.com/consultancy/) are available from [GitLab.com](http://www.gitlab.com/). | |
| 7 | +Issues and pull requests not in line with the guidelines listed in this document will be closed with just a link to this paragraph. GitLab is a popular open source project and the capacity to deal with issues and pull requests is limited. To get support for your problems please use other channels as detailed in [the getting help section of the readme](https://github.com/gitlabhq/gitlabhq#getting-help). Professional [support subscriptions](http://www.gitlab.com/subscription/) and [consulting services](http://www.gitlab.com/consultancy/) are available from [GitLab.com](http://www.gitlab.com/). | |
| 8 | + | |
| 9 | +## Issue tracker | |
| 10 | + | |
| 11 | +The [issue tracker](https://github.com/gitlabhq/gitlabhq/issues) is only for obvious bugs or misbehavior in the master branch of GitLab. When submitting an issue please conform to the issue submission guidelines listed below. | |
| 12 | + | |
| 13 | +Please send a pull request with a tested solution or a pull request with a failing test instead of opening an issue if you can. If you're unsure where to post, post to the [Support Forum](https://groups.google.com/forum/#!forum/gitlabhq) 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. | |
| 14 | + | |
| 15 | +### Issue tracker guidelines | |
| 16 | + | |
| 17 | +**Search** for similar entries before submitting your own, there's a good chance somebody else had the same issue or idea. Show your support with `:+1:` and/or join the discussion. | |
| 18 | + | |
| 19 | +* Summarize your issue in one sentence (what goes wrong, what did you expect to happen) | |
| 20 | +* Describe your issue in detail | |
| 21 | +* How can we reproduce the issue on the [GitLab Vagrant virtual machine](https://github.com/gitlabhq/gitlab-vagrant-vm) (start with: vagrant destroy && vagrant up && vagrant ssh) | |
| 22 | +* Add the last commit sha1 of the GitLab version you used to replicate the issue | |
| 23 | +* Add logs or screen shots when possible | |
| 24 | +* Link to the line of code that might be responsible for the problem | |
| 25 | +* Describe your setup (use relevant parts from `sudo -u gitlab -H bundle exec rake gitlab:env:info`) | |
| 8 | 26 | |
| 9 | 27 | ## Pull requests |
| 10 | 28 | |
| ... | ... | @@ -33,21 +51,3 @@ We will accept pull requests if: |
| 33 | 51 | * If it makes changes to the UI the pull request should include screenshots |
| 34 | 52 | |
| 35 | 53 | For examples of feedback on pull requests please look at already [closed pull requests](https://github.com/gitlabhq/gitlabhq/pulls?direction=desc&page=1&sort=created&state=closed). |
| 36 | - | |
| 37 | -## Issue tracker | |
| 38 | - | |
| 39 | -The [issue tracker](https://github.com/gitlabhq/gitlabhq/issues) is only for obvious bugs or misbehavior in the master branch of GitLab. When submitting an issue please conform to the issue submission guidelines listed below. | |
| 40 | - | |
| 41 | -Please send a pull request with a tested solution or a pull request with a failing test instead of opening an issue if you can. If you're unsure where to post, post to the [Support Forum](https://groups.google.com/forum/#!forum/gitlabhq) 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. | |
| 42 | - | |
| 43 | -### Issue tracker guidelines | |
| 44 | - | |
| 45 | -**Search** for similar entries before submitting your own, there's a good chance somebody else had the same issue or idea. Show your support with `:+1:` and/or join the discussion. | |
| 46 | - | |
| 47 | -* Summarize your issue in one sentence (what goes wrong, what did you expect to happen) | |
| 48 | -* Describe your issue in detail | |
| 49 | -* How can we reproduce the issue on the [GitLab Vagrant virtual machine](https://github.com/gitlabhq/gitlab-vagrant-vm) (start with: vagrant destroy && vagrant up && vagrant ssh) | |
| 50 | -* Add the last commit sha1 of the GitLab version you used to replicate the issue | |
| 51 | -* Add logs or screen shots when possible | |
| 52 | -* Link to the line of code that might be responsible for the problem | |
| 53 | -* Describe your setup (use relevant parts from `sudo -u gitlab -H bundle exec rake gitlab:env:info`) | ... | ... |