mirror of
https://github.com/pomerium/pomerium.git
synced 2025-04-28 18:06:34 +02:00
Update the PR template to better reflect our current workflow: - Do not suggest using the "Fixes" keyword, as this will close linked issues upon merge. (For most issues, the process is to let QA verify and then close the issue.) - Remove the "updated docs" and "updated UPGRADING.md" checklist steps. As documentation lives in a separate repository, it is no longer possible to update docs in the same PR. - Expand the list of labels, based on the changelog categories (omitting "security" because security issues should be reported separately)
28 lines
692 B
Text
28 lines
692 B
Text
## Summary
|
|
|
|
<!-- For example...
|
|
The existing implementation has poor numerical properties for
|
|
large arguments, so use the McGillicutty algorithm to improve
|
|
accuracy above 1e10.
|
|
|
|
The algorithm is described at https://wikipedia.org/wiki/McGillicutty_Algorithm
|
|
-->
|
|
|
|
## Related issues
|
|
|
|
<!-- For example...
|
|
- #159
|
|
-->
|
|
|
|
## User Explanation
|
|
|
|
<!-- How would you explain this change to the user? If this
|
|
change doesn't create any user-facing changes, you can leave
|
|
this blank. If filled out, add the `docs` label -->
|
|
|
|
## Checklist
|
|
|
|
- [ ] reference any related issues
|
|
- [ ] updated unit tests
|
|
- [ ] add appropriate label (`enhancement`, `bug`, `breaking`, `dependencies`, `ci`)
|
|
- [ ] ready for review
|