-
Notifications
You must be signed in to change notification settings - Fork 136
Add a pull request template #7231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Includes a checklist for contributors
mdellweg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With mkdocs, there's a way to move all the links into a references section in the end, if you want to make the bulk "more readable".
| 4. If the PR is a simple feature or a bugfix, please [`rebase and squash`](site:pulpcore/docs/dev/guides/git/#markdown-header-rebasing-and-squashing) to a single commit. If the PR | ||
| is a complex feature, make sure that all commits are cleanly separated and have meaningful commit messages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 4. If the PR is a simple feature or a bugfix, please [`rebase and squash`](site:pulpcore/docs/dev/guides/git/#markdown-header-rebasing-and-squashing) to a single commit. If the PR | |
| is a complex feature, make sure that all commits are cleanly separated and have meaningful commit messages. | |
| 4. If the PR is a simple feature or a bugfix, please [`rebase and squash`](site:pulpcore/docs/dev/guides/git/#markdown-header-rebasing-and-squashing) to a single commit. | |
| If the PR is a complex feature, make sure that all commits are cleanly separated and have meaningful commit messages. |
| {doc}`file an issue</bugs-features>`. | ||
| 4. If the PR is a simple feature or a bugfix, please [`rebase and squash`](site:pulpcore/docs/dev/guides/git/#markdown-header-rebasing-and-squashing) to a single commit. If the PR | ||
| is a complex feature, make sure that all commits are cleanly separated and have meaningful commit messages. | ||
| 5. Make sure you tag commits with `closes #IssueNumber` or `ref #IssueNumber` when working on a tracked issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 5. Make sure you tag commits with `closes #IssueNumber` or `ref #IssueNumber` when working on a tracked issue | |
| 5. Make sure you tag commits with `closes #IssueNumber` or `ref #IssueNumber` when working on a tracked issue. |
| 4. If the PR is a simple feature or a bugfix, please [`rebase and squash`](site:pulpcore/docs/dev/guides/git/#markdown-header-rebasing-and-squashing) to a single commit. If the PR | ||
| is a complex feature, make sure that all commits are cleanly separated and have meaningful commit messages. | ||
| 5. Make sure you tag commits with `closes #IssueNumber` or `ref #IssueNumber` when working on a tracked issue | ||
| 6. If AI was used, please make sure you are following the [Pulp policy on AI Usage](site:help/more/governance/ai_policy/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 6. If AI was used, please make sure you are following the [Pulp policy on AI Usage](site:help/more/governance/ai_policy/) | |
| 6. If AI was used, please make sure you are following the [Pulp policy on AI Usage](site:help/more/governance/ai_policy/). |
We don't use "please" anywhere else.
| 8. If the change requires a corresponding change in pulp-cli, open a PR against the pulp-cli or docs, or | ||
| `file an issue`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 8. If the change requires a corresponding change in pulp-cli, open a PR against the pulp-cli or docs, or | |
| `file an issue`. | |
| 8. If the change requires a corresponding change in pulp-cli, open a PR against the pulp-cli. |
Let's not make it sound as if you could just push out the work to someone else. If it's "required" it "should be done".
Includes a checklist for contributors
📜 Checklist