Open
Bug 1897545
Opened 1 year ago
Updated 1 year ago
Make the pull request template less demanding and more user-friendly
Categories
(Bugzilla :: Bugzilla-General, enhancement)
Bugzilla
Bugzilla-General
Tracking
()
NEW
People
(Reporter: justdave, Unassigned)
Details
Attachments
(2 files)
Bug 1893853 was a little bit of a knee-jerk reaction. And it didn't get committed in enough places. The message asking for a bug to be filed to go with the pull request sounds a bit abbrasive and elitist to me in hindsight. Let's clean it up to be user-friendly.
Comment 1•1 year ago
|
||
| Reporter | ||
Comment 2•1 year ago
|
||
New text:
<!--
#### Instructions
1. All pull requests to an officially supported branch must be accompanied by a bug report on bugzilla.mozilla.org. Please stop and file one there if you haven't already, or look for an existing one that fits what you're doing (the bug entry form will automatically search for things that look similar to the Summary you enter).
File a bug report: https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla
2. GitHub will automatically attach your pull request to the bug report in Bugzilla if you have "Bug #######" in the title of the pull request, where ####### is the bug number. For readability, we recommend putting it at the beginning of the title.
3. If it's not otherwise obvious from the title which branch the pull request applies to, please put the name of the branch in square brackets at the beginning of the title.
Example title:
[5.2] Bug 1234: Change Foo to do Bar
-->
#### Details
<!-- Explain what you did -->
This PR fixes/adds a feature...
#### Additional info
<!-- Paste the bug number after the # and after the = in the following line. -->
* [bug#](https://bugzilla.mozilla.org/show_bug.cgi?id=)
#### Test Plan
<!-- How did you verify the fix/feature in steps -->
1. Open the show_bug view
2. Edit the bug
3. ...
Comment 3•1 year ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•