summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorYves Senn <yves.senn@gmail.com>2013-04-16 18:05:05 +0200
committerYves Senn <yves.senn@gmail.com>2013-04-16 18:06:57 +0200
commit93ec507d19ca1124cb651149cf56181bb4ec79a2 (patch)
tree4c566c44d319eedce98129cb71afd83790952dc6 /CONTRIBUTING.md
parent211c433cd89ddc49b1f8c3ef6ba7bc366428a851 (diff)
downloadgitlab-ce-93ec507d19ca1124cb651149cf56181bb4ec79a2.tar.gz
contribution guidelines: no feature requests on the Github issue tracker
State clearly that the issue tracker is not used for feature requests and link to http://feedback.gitlab.com.
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e4b71d5b99a..79e57558084 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -10,6 +10,9 @@ Issues and pull requests not in line with the guidelines listed in this document
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.
+Do not use the issue tracker for feature requests. We have a specific
+[Feedback and suggestions forum](http://feedback.gitlab.com) for this purpose.
+
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.
### Issue tracker guidelines