|
1 | 1 | <!-- |
2 | 2 | Thanks for sending a pull request! |
3 | 3 |
|
4 | | -Please make sure you've read our contributing guidelines and how to submit a pull request (https://github.com/containers/podman/blob/main/CONTRIBUTING.md#submitting-pull-requests). |
5 | | -
|
6 | | -Finally, be sure to sign commits with your real name. Since by opening |
7 | | -a PR you already have commits, you can add signatures if needed with |
8 | | -something like `git commit -s --amend`. |
| 4 | +For more detailed information, please review our contributing guidelines: |
| 5 | +https://github.com/containers/podman/blob/main/CONTRIBUTING.md#submitting-pull-requests |
9 | 6 | --> |
10 | 7 |
|
| 8 | +#### Checklist |
| 9 | + |
| 10 | +Ensure you have completed the following checklist for your pull request to be reviewed: |
| 11 | +<!-- Use [x] to mark as done, or click the checkbox after opening PR --> |
| 12 | + |
| 13 | +- [ ] Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all |
| 14 | +commits. (`git commit -s`). (If needed, use `git commit -s --amend`). The author email must match |
| 15 | +the sign-off email address. See [CONTRIBUTING.md](https://github.com/containers/podman/blob/main/CONTRIBUTING.md#sign-your-prs) |
| 16 | +for more information. |
| 17 | +- [ ] Referenced issues using `Fixes: #00000` in commit message (if applicable) |
| 18 | +- [ ] [Tests](https://github.com/containers/podman/tree/main/test#readme) have been added/updated (or no tests are needed) |
| 19 | +- [ ] [Documentation](https://github.com/containers/podman/blob/main/docs/README.md) has been updated (or no documentation changes are needed) |
| 20 | +- [ ] All commits pass `make validatepr` (format/lint checks) |
| 21 | +- [ ] [Release note](https://github.com/kubernetes/community/blob/master/contributors/guide/release-notes.md) entered in the section below (or `None` if no user-facing changes) |
| 22 | + |
11 | 23 | #### Does this PR introduce a user-facing change? |
12 | 24 |
|
13 | 25 | <!-- |
14 | | -If no, just write `None` in the release-note block below. If yes, a release note |
15 | | -is required: Enter your extended release note in the block below. If the PR |
16 | | -requires additional action from users switching to the new release, include the |
17 | | -string "action required". |
18 | | -
|
19 | | -For more information on release notes, please follow the Kubernetes model: |
20 | | -https://git.k8s.io/community/contributors/guide/release-notes.md |
| 26 | +Write `None` if there are no user-facing changes, otherwise enter your release note below. |
| 27 | +Include "action required" if users need to take action when upgrading. |
21 | 28 | --> |
22 | 29 |
|
23 | 30 | ```release-note |
|
0 commit comments