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 README #34

Merged
merged 1 commit into from
Nov 1, 2017
Merged

Update README #34

merged 1 commit into from
Nov 1, 2017

Conversation

joyeecheung
Copy link
Member

No description provided.

@codecov-io
Copy link

codecov-io commented Nov 1, 2017

Codecov Report

Merging #34 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #34   +/-   ##
=======================================
  Coverage   79.88%   79.88%           
=======================================
  Files          10       10           
  Lines         353      353           
=======================================
  Hits          282      282           
  Misses         71       71

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 86702da...0db7a4d. Read the comment docs.

@@ -44,8 +47,7 @@ This one is inspired by Evan Lucas's [node-review](https://github.com/evanlucas/
- [x] Generate `Fixes`
- [x] Generate `Refs`
- [x] Check for CI runs
- [ ] Check if commiters match authors
- Only when `"authorAssociation": "FIRST_TIME_CONTRIBUTOR"`
- [x] Check if commiters match authors
- [x] Check 48-hour wait
- [x] Check two TSC approval for semver-major
- [ ] Warn new commits after reviews
Copy link
Member Author

Choose a reason for hiding this comment

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

Hmm..also I am not quite sure how this one should be handled because in practice, we still count reviews that give approval before new commits, as long as they don't object afterwards.

Copy link
Contributor

Choose a reason for hiding this comment

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

So, there was a conversation at some point that people who comment "LGTM" want that to be dismissed if a new commit comes in.
nodejs/node#13413 (comment)

Copy link
Member Author

Choose a reason for hiding this comment

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

Hmm..I think I can not get a conclusion from that thread, or did I miss something? Should we open an issue in the core repo to get this settled?

@joyeecheung joyeecheung merged commit b0d428d into master Nov 1, 2017
@joyeecheung joyeecheung deleted the update-readme branch November 11, 2017 04:45
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