Skip to content

Commit 8574160

Browse files
authored
Merge pull request #369 from rstudio/update-pull-request-template
Updates pull request template
2 parents 022d196 + b05a333 commit 8574160

File tree

1 file changed

+23
-23
lines changed

1 file changed

+23
-23
lines changed

.github/pull_request_template.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,33 +1,33 @@
1-
<!--- Provide a general summary of your changes in the title. -->
1+
<!-- Provide a general summary of your changes in the title. -->
2+
<!-- Examples: Updates pull request template -->
23

3-
## Description
4-
<!--- Please describe the problem you are addressing and your proposed changes. -->
4+
## Intent
5+
<!-- Describe what problem you are addressing in this pull request. -->
6+
<!-- If this change is associated with an open issue, please link to it here. -->
7+
<!-- Example: "Resolves #24" -->
8+
<!-- See https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue -->
59

6-
## Motivation and Context
7-
<!--- Even small changes deserve a little attention to detail. -->
8-
<!--- Why is this change required? What problem does it solve? -->
9-
<!--- If it fixes an open issue, please link to the issue here. -->
10-
<!--- Example: "Addresses Issue # 1" -->
10+
## Type of Change
11+
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply. -->
12+
<!-- If you check more than one box, you may need to refactor this change into separate pull requests -->
1113

12-
## How Has This Been Tested?
13-
<!--- Please describe in detail how you tested your changes. -->
14-
<!--- Automation should be used to verify that a change remains in place. -->
15-
<!--- Automated tests should be included in this pull request. -->
14+
- [ ] Bug Fix <!-- A change which fixes an existing issue -->
15+
- [ ] New Feature <!-- A change which adds additional functionality -->
16+
- [ ] Breaking Change <!-- A breaking change which causes existing functionality to change -->
1617

17-
<!--- If applicable, enumerate the steps that someone can take to exercise this change manually. -->
18-
<!--- Please include details of your testing environment. -->
19-
<!--- Detail is important! -->
18+
## Approach
19+
<!-- Describe how you solved this problem and any trade-offs you encountered. -->
20+
<!-- Link any additional documentation associated with this change here -->
2021

21-
### Screenshots (if appropriate):
22+
## Automated Tests
23+
<!-- Describe the automated tests associated with this change. -->
24+
<!-- If automated tests are not included in this change, please state why. -->
2225

23-
## Types of Changes
24-
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply. -->
25-
- [ ] Bug fix (non-breaking change which fixes an issue)
26-
- [ ] New feature (non-breaking change which adds functionality)
27-
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
26+
## Directions for Reviewers
27+
<!-- Provide steps for reviewers to validate this change manually. -->
2828

29-
## Checklist:
29+
## Checklist
3030
<!--- Go over all the following points, and put an `x` in all the boxes that apply: -->
3131
<!--- If you need clarification on any of these, feel free to ask. We're here to help! -->
32-
- [ ] I have added tests to cover my changes.
3332
- [ ] I have updated [CHANGELOG.md](../CHANGELOG.md) to cover notable changes.
33+
- [ ] I have updated all related GitHub issues to reflect their current state.

0 commit comments

Comments
 (0)