-
Alexander Popiak authored
* mention C and M labels in contributing guide * update PR template with more specific instructions * update PR template with updated label rules and contributing guide link * update contibuting guide
a1709717
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
PULL_REQUEST_TEMPLATE.md 1.54 KiB
Thank you for your Pull Request!
Before you submitting, please check that:
-
You added a brief description of the PR, e.g.:
- What does it do?
- What important points reviewers should know?
- Is there something left for follow-up PRs?
-
You labeled the PR appropriately if you have permissions to do so:
-
A*for PR status (one required) -
B*for changelog (one required) -
C*for release notes (exactly one required) -
D*for various implications/requirements - Github's project assignment
-
-
You mentioned a related issue if this PR related to it, e.g.
Fixes #228orRelated #1337. - You asked any particular reviewers to review. If you aren't sure, start with GH suggestions.
-
Your PR adheres to the style guide
- In particular, mind the maximal line length of 100 (120 in exceptional circumstances).
- There is no commented code checked in unless necessary.
- Any panickers have a proof or removed.
- You bumped the runtime version if there are breaking changes in the runtime.
- You updated any rustdocs which may have changed
- Has the PR altered the external API or interfaces used by Polkadot? Do you have the corresponding Polkadot PR ready?
Refer to the contributing guide for details.
After you've read this notice feel free to remove it. Thank you!
✄ -----------------------------------------------------------------------------