summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDouwe Maan <douwe@gitlab.com>2016-05-04 14:46:24 +0000
committerDouwe Maan <douwe@gitlab.com>2016-05-04 14:46:24 +0000
commit72e4bd5fc40c3b61792bf5f8897ab881775c7146 (patch)
tree6bd58017cb3eb6d19a4d714156fc02d0b278e0c1
parent836eb04b1a4d9ce8a3c7e915299133611d8e21ae (diff)
parent52a6b976a77d9ede9f1b50d55e33824ed05acb5f (diff)
downloadgitlab-ce-72e4bd5fc40c3b61792bf5f8897ab881775c7146.tar.gz
Merge branch 'feature-proposal-contribution-guidelines' into 'master'
feature proposal issue template in contributing guide This adds a feature proposal template to the contribution guidelines for internal and external use. Fixes #15448 cc @markpundsack @stanhu @dzaporozhets See merge request !3967
-rw-r--r--CONTRIBUTING.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ed565b0e573..9fe4cf7b0f6 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -142,6 +142,16 @@ code snippet right after your description in a new line: `~"feature proposal"`.
Please keep feature proposals as small and simple as possible, complex ones
might be edited to make them small and simple.
+You are encouraged to use the template below for feature proposals.
+
+```
+## Description including problem, use cases, benefits, and/or goals
+
+## Proposal
+
+## Links / references
+```
+
For changes in the interface, it can be helpful to create a mockup first.
If you want to create something yourself, consider opening an issue first to
discuss whether it is interesting to include this in GitLab.