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

PR review policy #923

Merged
merged 6 commits into from
Apr 23, 2017
Merged

Conversation

shilman
Copy link
Member

@shilman shilman commented Apr 20, 2017

Issue: N/A

What I did

Quick pass at reviewer policy after short chat with @tmeasday

Improvements welcome! Since this is a policy change, I'll wait for two approving reviews before I merge.

How to test

N/A

shilman added 2 commits April 19, 2017 20:28
Quick pass at reviewer policy after short chat with @tmeasday
@shilman
Copy link
Member Author

shilman commented Apr 20, 2017

pr_review_policy_by_shilman_ _pull_request__923_ _storybooks_storybook

@tmeasday

CONTRIBUTING.md Outdated
@@ -56,9 +56,9 @@ Before you submit a new PR, make you to run `npm test`. Do not submit a PR if te

### Reviewing PRs

**As a PR submitter**, you should reference the issue if there is one, include a short description of what you contributed and, if it is a code change, instructions for how to manually test out the change. This is informally enforced by our [PR template](https://github.com/storybooks/storybook/blob/master/.github/PULL_REQUEST_TEMPLATE.md).
**As a PR submitter**, you should reference the issue if there is one, include a short description of what you contributed and, if it is a code change, instructions for how to manually test out the change. This is informally enforced by our [PR template](https://github.com/storybooks/storybook/blob/master/.github/PULL_REQUEST_TEMPLATE.md). If you have merge rights and the changes are trivial, feel free to force merge without a review.
Copy link
Member

Choose a reason for hiding this comment

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

This isn't quite what I meant.

What I meant was:

If your PR is reviewed as only needing trivial changes (e.g. small typos etc), and you have commit access, then you can merge the PR after making those changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants