summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Rodríguez <deivid.rodriguez@riseup.net>2020-01-15 10:11:40 +0100
committerDavid Rodríguez <deivid.rodriguez@riseup.net>2020-01-15 10:11:40 +0100
commit2fdfe019126dfbb066286625e08380a627374846 (patch)
tree8920d418d7bf47c9fc379a0d1bfd579846f9ccf8
parent6bd3642718f527b7e02ac5dfe5cac8c36c6d0bcb (diff)
downloadbundler-2fdfe019126dfbb066286625e08380a627374846.tar.gz
Squash last three questions into just one
In my experience, for most PRs it is enough to just explain the problem and explain your fix, and most times it's a bit artificial to fill out all 4 questions. So, I'm squashing them.
-rw-r--r--.github/PULL_REQUEST_TEMPLATE.md12
1 files changed, 3 insertions, 9 deletions
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 6fa31f8b2c..ebe0de95a5 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -5,14 +5,8 @@ To make reviewing this PR a bit easier, please fill out answers to the following
<!-- Write a clear and complete description of the problem -->
-### What was your diagnosis of the problem?
-
-<!-- Explain the investigation you made to determine the cause of the issue and your conclusions -->
-
### What is your fix for the problem, implemented in this PR?
-<!-- Explain the fix being implemented -->
-
-### Why did you choose this fix out of the possible options?
-
-<!-- If you considered other alternatives, explain why you end up choosing the current implementation -->
+<!-- Explain the fix being implemented. Include any diagnosis you run to
+determine the cause of the issue and your conclusions. If you considered other
+alternatives, explain why you end up choosing the current implementation -->