-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Proposal for PR template #542
Conversation
Arguments against this style of PR: it introduces noise because EVERY PR will have a checklist. However on balance I think it's helpful, especially for new contributors. Also we don't really seem to use checklists much otherwise. |
I can definitely see this being useful to first time contributors, especially if we actually had more boxes to tick. Not sure how much value this adds at this exact moment though, since the only thing it reminds users to do is describe the PR and update the CHANGELOG. Maybe a box for "adds appropriate tests"? Let's discuss tomorrow. |
I agree with adds tests. However I think having the "What does this do?" and "Why is this important" headers is important. Even for people familiar with contributing, it's helpful to have these prompts -- I'm thinking of myself; I'm definitely guilty of skipping the "what" and "why" in some of my PRs. My experience is that especially with open-source projects, there's a lot of PRs which essentially say "Hey, read the code to know what changed!" and a small amount of prompts can mitigate that attitude. |
The flip side of that is sometimes you see these monstrosity PR templates where it's a whole page and as a contributor, you have to read it every time to figure out what you're supposed to do and where you're supposed to write it; as a maintainer you have to parse it every time to see what you wrote and what the contributor wrote... it's bad. I'd like to strike a balance between minimal guidance that leads to a more effective PR description. |
I'm not opposed to this style of PR. Definitely the What/Why is much needed and the changelog checkbox to keep us in tune with updating it are nice to have |
The more I look at the progress bars in the PRs the more I actually like it. I've seen in other repositories where PR creators have slash commands like |
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.
I'm cool with this for now
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.
Could you add a checkbox for "updates docs/outline.toml
if any new public methods / functions (or 'user-facing methods / functions') were added"
@cicdw thoughts on new update? |
4840d5a
to
d0e5ccb
Compare
Clarify messaging on timeout states
Thanks for contributing to Prefect!
Please describe your work and make sure your PR:
CHANGELOG.md
(if appropriate)docs/outline.toml
to include API docs for any new functions or arguments (if appropriate)What does this PR change?
Why is this PR important?