Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit b308f7c

Browse files
Minor changes
1 parent 4fdc92e commit b308f7c

File tree

1 file changed

+16
-25
lines changed

1 file changed

+16
-25
lines changed

‎docs/git/pull-request-template.md

Lines changed: 16 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -3,61 +3,52 @@ id: pull-request-template
33
title: Pull Request Template
44
---
55

6-
76
# Generic Pull Request Template
87

9-
Add a file called pull_request_template.md to the root directory of your repository
8+
Add a file called `pull_request_template.md` to the root directory of your repository. Take a look at number of ways you can do this in GitHub. https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository
109

1110
## Title
11+
1212
‍‍‍Provide a general summary of your changes in the title.
1313

1414
## Description
1515

16-
Describe your changes in detail
16+
Describe your changes in detail. Link to the related issue ticket.
1717

18-
## Motivation, context and link to the ticket
18+
## Context
1919

2020
Why is this change required? What problem does it solve?
21-
Link to the related Jira ticket.
21+
2222

2323
## Related PRs
24+
2425
Link to related pull requests
2526

2627
## How has this been tested?
27-
Please describe in detail how you tested your changes.
2828

29-
Include details of your testing environment, and the tests you ran to
29+
Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran.
3030

31-
See how your change affects other areas of the code, etc.
32-
33-
## Screenshots (if appropriate):
31+
## Screenshots:
3432

33+
Add screenshots or video if applicable.
3534

3635
## Types of changes
36+
3737
What types of changes does your code introduce? Put an x in all the boxes that apply:
3838

3939
[ ] Bug fix (non-breaking change which fixes an issue)
40-
4140
[ ] New feature (non-breaking change which adds functionality)
42-
4341
[ ] Breaking change (fix or feature that would cause existing functionality to change)
44-
45-
[ ] Documentation Update (if none of the other choices apply)
42+
[] Documentation
43+
[ ] Tests
4644

4745
## Checklist
48-
Go over all the following points, and put an x in all the boxes that apply.
49-
If you're unsure about any of these, don't hesitate to ask. Your team members are there to help!
5046

51-
[] My code follows the code style of this project.
47+
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. Your team members are there to help!
5248

49+
[ ] My code follows the code style of this project.
5350
[ ] I have updated the documentation accordingly.
54-
5551
[ ] I have added tests to cover my changes.
56-
57-
[ ] All new and existing tests passed.
58-
5952
[ ] One or more required reviews requested.
60-
61-
[ ] Any dependent changes have been merged and published in downstream modules
62-
63-
[ ] I have updated and verified the database schema changes and related documentation have been updated.
53+
[ ] Any dependent changes have been merged and published in upstream modules.
54+
[ ] I have updated and verified the changes end-to-end and related documentation have been updated.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /