matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
master
sonic-buildimage/.github/pull_request_template.md

75 lines
2.0 KiB
Markdown
Raw Permalink Normal View History

[GitHub] Tweak PR and issue templates (#6744) Tweak GitHub issue and pull request templates - Rename files to align with new [standard](https://docs.github.com/en/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests) - Use markdown headings rather than bolded bullets
2021-02-11 01:12:21 -06:00
<!--
Please make sure you've read and understood our contributing guidelines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
** Make sure all your commits include a signature generated with `git commit -s` **
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx" or "resolves #xxxx"
Please provide the following information:
-->
#### Why I did it
Update pull request template for test evidence, and work item trackers (#14552) Update pull request template for test evidence, and work item trackers
2023-04-11 17:16:35 -05:00
##### Work item tracking
- Microsoft ADO **(number only)**:
[GitHub] Tweak PR and issue templates (#6744) Tweak GitHub issue and pull request templates - Rename files to align with new [standard](https://docs.github.com/en/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests) - Use markdown headings rather than bolded bullets
2021-02-11 01:12:21 -06:00
#### How I did it
#### How to verify it
Update pull request template for test evidence, and work item trackers (#14552) Update pull request template for test evidence, and work item trackers
2023-04-11 17:16:35 -05:00
<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->
[GitHub] Tweak PR and issue templates (#6744) Tweak GitHub issue and pull request templates - Rename files to align with new [standard](https://docs.github.com/en/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests) - Use markdown headings rather than bolded bullets
2021-02-11 01:12:21 -06:00
#### Which release branch to backport (provide reason below if selected)
<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->
- [ ] 201811
- [ ] 201911
- [ ] 202006
- [ ] 202012
[PR template] Add checkbox for backport request to 202106 branch (#7960) Add checkbox for backport request to 202106 branch to PR template
2021-06-29 20:45:23 -05:00
- [ ] 202106
Update template pull_request_template.md (#9888) Updating template description to include link to configuration schema for YANG module changes. #### Why I did it Updating template description to include link to configuration schema for YANG module changes. When reviewing yang models it becomes difficult to know the entire schema for the table for which yang is defined. Besides providing a clear picture, it will also help to document the config_db schema which is not upto date. #### How I did it Updating template file
2022-02-14 15:55:40 -06:00
- [ ] 202111
[github]: update pr template to include 202205 backport option (#11139) Signed-off-by: Guohan Lu <lguohan@gmail.com>
2022-06-14 13:48:59 -05:00
- [ ] 202205
Add 202211 backport option for the PR review template (#12884) Why I did it Add 202211 backport option How I did it Add option in .github/pull_request_template.md How to verify it
2022-12-02 03:43:56 -06:00
- [ ] 202211
To change the PR template to have 202305 (#15513) Why I did it To include 202305 in the PR template. Work item tracking Microsoft ADO (21450860): How I did it Change the temlate. How to verify it pass PR test.
2023-06-16 21:32:11 -05:00
- [ ] 202305
[GitHub] Tweak PR and issue templates (#6744) Tweak GitHub issue and pull request templates - Rename files to align with new [standard](https://docs.github.com/en/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests) - Use markdown headings rather than bolded bullets
2021-02-11 01:12:21 -06:00
Update pull request template for test evidence, and work item trackers (#14552) Update pull request template for test evidence, and work item trackers
2023-04-11 17:16:35 -05:00
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->
[GitHub] Tweak PR and issue templates (#6744) Tweak GitHub issue and pull request templates - Rename files to align with new [standard](https://docs.github.com/en/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests) - Use markdown headings rather than bolded bullets
2021-02-11 01:12:21 -06:00
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
Update pull request template for test evidence, and work item trackers (#14552) Update pull request template for test evidence, and work item trackers
2023-04-11 17:16:35 -05:00
<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->
[doc]: Updated PR Template for a comment to add label/tag for the feature raised. (#12058) Signed-off-by: kannankvs <kannan_kvs@dell.com>
2022-09-13 23:49:05 -05:00
Update template pull_request_template.md (#9888) Updating template description to include link to configuration schema for YANG module changes. #### Why I did it Updating template description to include link to configuration schema for YANG module changes. When reviewing yang models it becomes difficult to know the entire schema for the table for which yang is defined. Besides providing a clear picture, it will also help to document the config_db schema which is not upto date. #### How I did it Updating template file
2022-02-14 15:55:40 -06:00
#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
[Template]Update template to point to configuration.md in yang-models folder (#10777) … folder #### Why I did it Update template to point to configuration.md in yang-model folder.
2022-05-09 14:04:01 -05:00
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
Update template pull_request_template.md (#9888) Updating template description to include link to configuration schema for YANG module changes. #### Why I did it Updating template description to include link to configuration schema for YANG module changes. When reviewing yang models it becomes difficult to know the entire schema for the table for which yang is defined. Besides providing a clear picture, it will also help to document the config_db schema which is not upto date. #### How I did it Updating template file
2022-02-14 15:55:40 -06:00
-->
[GitHub] Tweak PR and issue templates (#6744) Tweak GitHub issue and pull request templates - Rename files to align with new [standard](https://docs.github.com/en/github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests) - Use markdown headings rather than bolded bullets
2021-02-11 01:12:21 -06:00
#### A picture of a cute animal (not mandatory but encouraged)
Reference in New Issue Copy Permalink