-
Notifications
You must be signed in to change notification settings - Fork 266
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
chore: update pull request template #1379
Conversation
This hopefully fits our current work better
.github/pull_request_template.md
Outdated
- [ ] The branch has been merged or rebased against the head of its merge target. | ||
- [ ] I'm happy for the PR to be merged at the reviewer's next convenience. | ||
- [ ] I have [linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this pull request to relevant issues (if any exist). | ||
- [ ] The branch is up-to-date (i.e. no Update Branch button). |
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.
Feel like this one doesn't make much sense, since it can be completed once you get the PR ready, but can fall out of date pretty quickly. But I'm fine keeping it for historic reasons.
I've removed that line. Let's chock it up to 'common git sense' and see how that fares. If someone doesn't know the reviewer can always hit Update Branch, so it should be fine. |
Another tweak to optimize for commit messages (removed description heading) |
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.
lgtm
This hopefully fits our current work better.