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

Update text in PR template #6188

Merged
merged 2 commits into from Nov 14, 2019
Merged

Update text in PR template #6188

merged 2 commits into from Nov 14, 2019

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented Nov 14, 2019

  • Target the master branch for bug fixes, documentation updates and trivial changes.
  • Target the features branch for new features, improvements, and removals/deprecations.
  • Include documentation when adding new features.
  • Include new tests or update existing tests when applicable.

Unless your change is trivial or a small documentation fix (e.g., a typo or reword of a small section) please:

  • [n/a, small docs fix] Create a new changelog file in the changelog folder, with a name like <ISSUE NUMBER>.<TYPE>.rst. See changelog/README.rst for details.
  • Add yourself to AUTHORS in alphabetical order;

  • The "(please delete...)" text is redundant and can be removed; it's inside comments so won't be shown anyway.

  • Replace the semicolon with a fullstop. It's not necessary here, you don't use them at the end of a sentence; they would only go in the middle of a sentence, a bit like a comma.

@hugovk hugovk added the type: docs documentation improvement, missing or needing clarification label Nov 14, 2019
@@ -2,15 +2,14 @@
Thanks for submitting a PR, your contribution is really appreciated!

Here is a quick checklist that should be present in PRs.
(please delete this text from the final description, this is just a guideline)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might be a misunderstanding then - I've assumed the whole text should be deleted - or at least we should not end up with open TODOs always (since you cannot target both master/features).
Can we have the closing --> at the end maybe, so everything becomes a comment / invisble?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, updated!

Copy link
Member

@nicoddemus nicoddemus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@blueyed blueyed merged commit d4e4ab5 into pytest-dev:master Nov 14, 2019
@blueyed
Copy link
Contributor

blueyed commented Nov 14, 2019

Thanks! ❤️

@asottile
Copy link
Member

hmmm if we're going to hide the checklist entirely what's the point? now I can't see if PRs are ready

@hugovk hugovk deleted the update-template branch November 15, 2019 10:42
@hugovk
Copy link
Member Author

hugovk commented Nov 15, 2019

An argument for hiding the checklist completely: you don't get these inconsistent progress bars.

image

An argument for keeping it: maintainers can see which tasks have been done.

image

Would it be best to keep the checklist visible, and something like this in the comment block?

Please delete the checkboxes which don't apply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: docs documentation improvement, missing or needing clarification
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants