summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJob van der Voort <job@gitlab.com>2016-07-14 14:39:00 +0000
committerJob van der Voort <job@gitlab.com>2016-07-14 14:39:00 +0000
commit005ce32f7ca8743465f797f43eb47e1745a006e9 (patch)
tree2b270764480bcf920d6faa920c466468f28453a2
parentf17a753d276e74840437143a27b8e769a52ad106 (diff)
parent81a34f2f5650ef64528867b78bab6a00ec177248 (diff)
downloadgitlab-ce-005ce32f7ca8743465f797f43eb47e1745a006e9.tar.gz
Merge branch 'cleanup-feature-proposal' into 'master'
Cleanup feature proposal template ## What does this MR do? Changes the recommended template for feature proposals. ## Are there points in the code the reviewer needs to double check? ## Why was this MR needed? I've been using the template for a while, and find that putting so many words into the h2 makes me think there's actual content there, until I realize I'm just reading the template text (again). I think we can get away with just putting `Description` as the header, and putting the suggested content for that section as plain text below for someone to replace. ## What are the relevant issue numbers? ## Screenshots (if relevant) ![image](/uploads/20a99c98a12aad84c1a7ec020f365b2f/image.png) /cc @JobV See merge request !5240
-rw-r--r--CONTRIBUTING.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f4472214778..14ff05c9aa3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -145,7 +145,8 @@ 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
+## Description
+Include problem, use cases, benefits, and/or goals
## Proposal