Skip to content
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

Merged
merged 9 commits into from
Jan 25, 2019
Merged

Proposal for PR template #542

merged 9 commits into from
Jan 25, 2019

Conversation

jlowin
Copy link
Member

@jlowin jlowin commented Jan 21, 2019

Thanks for contributing to Prefect!

Please describe your work and make sure your PR:

  • adds new tests (if appropriate)
  • updates CHANGELOG.md (if appropriate)
  • updates 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?

@jlowin jlowin requested review from cicdw and joshmeek as code owners January 21, 2019 15:30
@jlowin
Copy link
Member Author

jlowin commented Jan 21, 2019

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.

@cicdw
Copy link
Member

cicdw commented Jan 22, 2019

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.

@jlowin
Copy link
Member Author

jlowin commented Jan 22, 2019

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.

@jlowin
Copy link
Member Author

jlowin commented Jan 22, 2019

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.

@joshmeek
Copy link

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

@joshmeek
Copy link

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 /ready_for_review but the checkboxes seem to satisfy just that.

joshmeek
joshmeek previously approved these changes Jan 23, 2019
Copy link

@joshmeek joshmeek left a 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

joshmeek
joshmeek previously approved these changes Jan 23, 2019
joshmeek
joshmeek previously approved these changes Jan 24, 2019
Copy link
Member

@cicdw cicdw left a 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"

@jlowin
Copy link
Member Author

jlowin commented Jan 25, 2019

@cicdw thoughts on new update?

joshmeek
joshmeek previously approved these changes Jan 25, 2019
@jlowin jlowin merged commit afbe234 into master Jan 25, 2019
@jlowin jlowin deleted the jlowin-patch-1 branch January 25, 2019 21:02
cicdw pushed a commit that referenced this pull request Nov 5, 2021
Clarify messaging on timeout states
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants