[x] PR Name: Please name this PR in format of
[TICKET_ID]: [BRIEF DESCRIPTION]. For example: MONO-0000: Implement
component X to use with Y
[x] Ticket(s) and Related PR(s): Add the tickets that this PR will resolve
once merge. You can also add a list of related PR(s); this is useful when
to communicate that another PR must be reviewed first.
[x] Change Description: Please update the above change list to provide a
list of changes done. This will be added to the commit when merged for a
useful commit description.
This can be omitted in the rare case that the PR is very small and the title
alone clearly explains what it does.
[ ] Tests: All code should have strong tests. If you have questions about
this please ask one of the code owners. All tests need to pass CI for all
test matrix combinations for your PR to be considered for merge.
[ ] Code Owner Review: Please add at least one repository code owner as a
reviewer. You are welcome to add anyone else you'd like feedback from.
[ ] Squash Commit with Details: It's hard to keep a perfect commit record
so we prefer squash commits. When doing squash commits the commit name
should auto fill the the PR name (formatted as defined in the PR Name
section above) plus (#123) where the number is the PR number. Set the
commit paragraph text to be the changes list above (don't include
"Changes" header, just the list).
Ticket(s)
Related PR(s)
Changes
Checklist
[TICKET_ID]: [BRIEF DESCRIPTION]. For example: MONO-0000: Implement component X to use with Y(#123)where the number is the PR number. Set the commit paragraph text to be the changes list above (don't include "Changes" header, just the list).