Skip to content

Reorganize and update PR template #5106

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

Merged
merged 3 commits into from
Mar 8, 2017
Merged

Reorganize and update PR template #5106

merged 3 commits into from
Mar 8, 2017

Conversation

chrisvfritz
Copy link
Contributor

@chrisvfritz chrisvfritz commented Mar 6, 2017

Using the updated PR template below - so meta!

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe: contributor documentation update

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

The PR fulfills these requirements:

Other information:

  • Improved consistency of language in the template
  • Reorganized template a little
  • Added instructions at the top for how to check boxes

@codecov-io
Copy link

codecov-io commented Mar 6, 2017

Codecov Report

Merging #5106 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #5106   +/-   ##
=======================================
  Coverage   99.97%   99.97%           
=======================================
  Files          86       86           
  Lines        3508     3508           
=======================================
  Hits         3507     3507           
  Misses          1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2dc177f...00afe9c. Read the comment docs.

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

If fixing a **bug**, the PR's description includes:
Copy link
Member

Choose a reason for hiding this comment

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

I find this quite cumbersome if the issue is already opened with all these details. Isn't the When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number enough?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

What if we changed these two sub-headings to, "the PR's description or a linked to issue includes"?

Copy link
Member

Choose a reason for hiding this comment

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

I think that we should remove the whole block. I'm worried about the list being too long and scary for new contributors. Do we have PRs that try to fix bugs that doesn't exist?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You look at PRs on this repo more than I do, so if it's not solving a problem you commonly see, I agree it does make sense to remove it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done!

@yyx990803 yyx990803 merged commit 0bcad13 into dev Mar 8, 2017
@posva posva deleted the chrisvfritz-patch-1 branch May 9, 2017 08:47
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.

6 participants