travisn
cc2e8e6e60
Since nobody seems to see the instructions for opening a PR, make another attempt to clarify what someone should do when they are opening a PR. Signed-off-by: travisn <tnielsen@redhat.com>
21 lines
1.2 KiB
Markdown
21 lines
1.2 KiB
Markdown
<!-- Thank you for contributing to Rook! -->
|
|
|
|
<!-- STEPS TO FOLLOW:
|
|
1. Add a description of the changes (frequently the same as the commit description)
|
|
2. Enter the issue number next to "Resolves #" below (if there is no tracking issue resolved, **remove that section**)
|
|
3. Review our Contributing documentation at https://rook.io/docs/rook/latest/Contributing/development-flow/
|
|
4. Follow the steps in the checklist below, starting with the **Commit Message Formatting**.
|
|
-->
|
|
|
|
**Which issue is resolved by this Pull Request:**
|
|
Resolves #
|
|
|
|
**Checklist:**
|
|
|
|
- [ ] **Commit Message Formatting**: Commit titles and messages follow guidelines in the [developer guide](https://rook.io/docs/rook/latest/Contributing/development-flow/#commit-structure).
|
|
- [ ] Reviewed the developer guide on [Submitting a Pull Request](https://rook.io/docs/rook/latest/Contributing/development-flow/#submitting-a-pull-request)
|
|
- [ ] [Pending release notes](https://github.com/rook/rook/blob/master/PendingReleaseNotes.md) updated with breaking and/or notable changes for the next minor release.
|
|
- [ ] Documentation has been updated, if necessary.
|
|
- [ ] Unit tests have been added, if necessary.
|
|
- [ ] Integration tests have been added, if necessary.
|