Skip to content

Commit

Permalink
Remove the is-ready-to-merge question from PR template
Browse files Browse the repository at this point in the history
GitHub now has "draft" pull requests so all new PR's should either
be draft or ready to merge.
  • Loading branch information
rafmudaf committed Jul 20, 2020
1 parent a77f4b9 commit 8a17cc5
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@

**Complete this sentence**
THIS PULL REQUEST __ [IS/IS NOT] __ READY TO MERGE
<!-- Is this pull request ready to be merged? -->
<!-- i.e. tests pass or are expected to fail; all development is finished; appropriate documentation is included. -->
<!-- If not but opening the pull request will facilitate development, make it a "draft" pull request -->

**Feature or improvement description**
<A clear and concise description of the new code.>
<!-- A clear and concise description of the new code. -->

**Related issue, if one exists**
<Link to a related GitHub Issue.>
<!-- Link to a related GitHub Issue. -->

**Impacted areas of the software**
<List any modules or other areas which should be impacted by this pull request. This helps to determine the verification tests.>
<!-- List any modules or other areas which should be impacted by this pull request. This helps to determine the verification tests. -->

**Additional supporting information**
<Add any other context about the problem here.>
<!-- Add any other context about the problem here. -->

**Test results, if applicable**
<Add the results from unit tests and regression tests here along with justification for any failing test cases.>
<!-- Add the results from unit tests and regression tests here along with justification for any failing test cases. -->

0 comments on commit 8a17cc5

Please sign in to comment.