Skip to content

Commit 7d60cc6

Browse files
authored
Merge pull request RooCodeInc#1272 from RooVetGit/pr-template
Update pull_request_template.md
2 parents 1750247 + 87785bb commit 7d60cc6

File tree

1 file changed

+20
-22
lines changed

1 file changed

+20
-22
lines changed

.github/pull_request_template.md

Lines changed: 20 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,35 @@
1-
<!-- **Note:** Consider creating PRs as a DRAFT. For early feedback and self-review. -->
1+
## Context
22

3-
## Description
3+
<!-- Brief description of WHAT you’re doing and WHY. -->
44

5-
## Type of change
5+
## Implementation
66

7-
<!-- Please ignore options that are not relevant -->
7+
<!--
88
9-
- [ ] Bug fix (non-breaking change which fixes an issue)
10-
- [ ] New feature
11-
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
12-
- [ ] This change requires a documentation update
9+
Some description of HOW you achieved it. Perhaps give a high level description of the program flow. Did you need to refactor something? What tradeoffs did you take? Are there things in here which you’d particularly like people to pay close attention to?
1310
14-
## How Has This Been Tested?
11+
-->
1512

16-
<!-- Please describe the tests that you ran to verify your changes -->
13+
## Screenshots
1714

18-
## Checklist:
15+
| before | after |
16+
| ------ | ----- |
17+
| | |
1918

20-
<!-- Go over all the following points, and put an `x` in all the boxes that apply -->
19+
## How to Test
2120

22-
- [ ] My code follows the patterns of this project
23-
- [ ] I have performed a self-review of my own code
24-
- [ ] I have commented my code, particularly in hard-to-understand areas
25-
- [ ] I have made corresponding changes to the documentation
21+
<!--
2622
27-
## Additional context
23+
A straightforward scenario of how to test your changes will help reviewers that are not familiar with the part of the code that you are changing but want to see it in action. This section can include a description or step-by-step instructions of how to get to the state of v2 that your change affects.
2824
29-
<!-- Add any other context or screenshots about the pull request here -->
25+
A "How To Test" section can look something like this:
3026
31-
## Related Issues
27+
- Sign in with a user with tracks
28+
- Activate `show_awesome_cat_gifs` feature (add `?feature.show_awesome_cat_gifs=1` to your URL)
29+
- You should see a GIF with cats dancing
3230
33-
<!-- List any related issues here. Use the GitHub issue linking syntax: #issue-number -->
31+
-->
3432

35-
## Reviewers
33+
## Get in Touch
3634

37-
<!-- @mention specific team members or individuals who should review this PR -->
35+
<!-- We'd love to have a way to chat with you about your changes if necessary. If you're in the [Roo Code Discord](https://discord.gg/roocode), please share your handle here. -->

0 commit comments

Comments
 (0)