vcpkg/.github/pull_request_template.md

<!-- If your PR fixes issues, please note that here by adding "Fixes #NNNNNN." for each fixed issue on separate lines. -->

<!-- If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/ -->

<!-- If this PR updates an existing port, please uncomment and fill out this checklist:

- [ ] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/maintainer-guide.md)
- [ ] SHA512s are updated for each updated download
- [ ] The "supports" clause reflects platforms that may be fixed by this new version
- [ ] Any fixed [CI baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt) entries are removed from that file.
- [ ] Any patches that are no longer applied are deleted from the port's directory.
- [ ] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result.
- [ ] Only one version is added to each modified port's versions file.

END OF PORT UPDATE CHECKLIST (delete this line) -->

<!-- If this PR adds a new port, please uncomment and fill out this checklist:

- [ ] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/maintainer-guide.md)
- [ ] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
- [ ] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all `find_package` calls are REQUIRED, are satisfied by `vcpkg.json`'s declared dependencies, or disabled with [CMAKE_DISABLE_FIND_PACKAGE_Xxx](https://cmake.org/cmake/help/latest/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html)
- [ ] The versioning scheme in `vcpkg.json` matches what upstream says.
- [ ] The license declaration in `vcpkg.json` matches what upstream says.
- [ ] The installed as the "copyright" file matches what upstream says.
- [ ] The source code of the component installed comes from an authoritative source.
- [ ] The generated "usage text" is accurate. See docs/examples/adding-an-explicit-usage.md for context.
- [ ] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result.
- [ ] Only one version is in the new port's versions file.
- [ ] Only one version is added to each modified port's versions file.

END OF NEW PORT CHECKLIST (delete this line) -->
Add a new-port checklist to the new PR template. (#27447) * Add a new-port checklist to the new PR template. I have observed many people tend to "tune out" our current pull request template, including maintainers, who don't even look at the content and sometimes miss important things people are trying to tell us. To that end, I would like to replace it with something more useful, including things for people submitting the most common kinds of PRs to check. * Apply fixes suggested by @vicroms and @PhoebeHui 2023-01-20 08:59:05 +08:00			`<!-- If your PR fixes issues, please note that here by adding "Fixes #NNNNNN." for each fixed issue on separate lines. -->`
[vcpkg] Add pull request template (#9280) * [vcpkg] Add pull request template * Update pull_request_template.md 2019-12-12 04:12:08 +08:00
Add a new-port checklist to the new PR template. (#27447) * Add a new-port checklist to the new PR template. I have observed many people tend to "tune out" our current pull request template, including maintainers, who don't even look at the content and sometimes miss important things people are trying to tell us. To that end, I would like to replace it with something more useful, including things for people submitting the most common kinds of PRs to check. * Apply fixes suggested by @vicroms and @PhoebeHui 2023-01-20 08:59:05 +08:00			`<!-- If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/ -->`
[vcpkg] Add pull request template (#9280) * [vcpkg] Add pull request template * Update pull_request_template.md 2019-12-12 04:12:08 +08:00
Add a new-port checklist to the new PR template. (#27447) * Add a new-port checklist to the new PR template. I have observed many people tend to "tune out" our current pull request template, including maintainers, who don't even look at the content and sometimes miss important things people are trying to tell us. To that end, I would like to replace it with something more useful, including things for people submitting the most common kinds of PRs to check. * Apply fixes suggested by @vicroms and @PhoebeHui 2023-01-20 08:59:05 +08:00			`<!-- If this PR updates an existing port, please uncomment and fill out this checklist:`
[vcpkg] Add pull request template (#9280) * [vcpkg] Add pull request template * Update pull_request_template.md 2019-12-12 04:12:08 +08:00
Add a new-port checklist to the new PR template. (#27447) * Add a new-port checklist to the new PR template. I have observed many people tend to "tune out" our current pull request template, including maintainers, who don't even look at the content and sometimes miss important things people are trying to tell us. To that end, I would like to replace it with something more useful, including things for people submitting the most common kinds of PRs to check. * Apply fixes suggested by @vicroms and @PhoebeHui 2023-01-20 08:59:05 +08:00			`- [ ] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/maintainer-guide.md)`
			`- [ ] SHA512s are updated for each updated download`
			`- [ ] The "supports" clause reflects platforms that may be fixed by this new version`
			`- [ ] Any fixed [CI baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt) entries are removed from that file.`
			`- [ ] Any patches that are no longer applied are deleted from the port's directory.`
			- [ ] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result.
			`- [ ] Only one version is added to each modified port's versions file.`
[vcpkg] improve pull request template (#17049) * improve pull request template * Update .github/pull_request_template.md: Apply suggestion Co-authored-by: Robert Schumacher <roschuma@microsoft.com> Co-authored-by: Robert Schumacher <roschuma@microsoft.com> 2021-04-13 04:42:44 +08:00
Add a new-port checklist to the new PR template. (#27447) * Add a new-port checklist to the new PR template. I have observed many people tend to "tune out" our current pull request template, including maintainers, who don't even look at the content and sometimes miss important things people are trying to tell us. To that end, I would like to replace it with something more useful, including things for people submitting the most common kinds of PRs to check. * Apply fixes suggested by @vicroms and @PhoebeHui 2023-01-20 08:59:05 +08:00			`END OF PORT UPDATE CHECKLIST (delete this line) -->`
[vcpkg] improve pull request template (#17049) * improve pull request template * Update .github/pull_request_template.md: Apply suggestion Co-authored-by: Robert Schumacher <roschuma@microsoft.com> Co-authored-by: Robert Schumacher <roschuma@microsoft.com> 2021-04-13 04:42:44 +08:00
Add a new-port checklist to the new PR template. (#27447) * Add a new-port checklist to the new PR template. I have observed many people tend to "tune out" our current pull request template, including maintainers, who don't even look at the content and sometimes miss important things people are trying to tell us. To that end, I would like to replace it with something more useful, including things for people submitting the most common kinds of PRs to check. * Apply fixes suggested by @vicroms and @PhoebeHui 2023-01-20 08:59:05 +08:00			`<!-- If this PR adds a new port, please uncomment and fill out this checklist:`

			`- [ ] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/maintainer-guide.md)`
			`- [ ] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.`
			- [ ] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all `find_package` calls are REQUIRED, are satisfied by `vcpkg.json`'s declared dependencies, or disabled with [CMAKE_DISABLE_FIND_PACKAGE_Xxx](https://cmake.org/cmake/help/latest/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html)
			- [ ] The versioning scheme in `vcpkg.json` matches what upstream says.
			- [ ] The license declaration in `vcpkg.json` matches what upstream says.
			`- [ ] The installed as the "copyright" file matches what upstream says.`
			`- [ ] The source code of the component installed comes from an authoritative source.`
			`- [ ] The generated "usage text" is accurate. See docs/examples/adding-an-explicit-usage.md for context.`
			- [ ] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result.
			`- [ ] Only one version is in the new port's versions file.`
			`- [ ] Only one version is added to each modified port's versions file.`

			`END OF NEW PORT CHECKLIST (delete this line) -->`