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

Adds note about two approval policy to PR template #10313

Merged
merged 2 commits into from Aug 12, 2019

Conversation

thiagoarrais
Copy link
Contributor

@thiagoarrais thiagoarrais commented Aug 9, 2019

Q                       A
Fixed Issues? None
Patch: Bug Fix? No
Major: Breaking Change? No
Minor: New Feature? No
Tests Added + Pass? N/A
Documentation PR Link
Any Dependency Changes? No
License MIT

I've sometimes noticed some folks getting confused about Babel's two approval policy. From the Contributor point of view, the PR seems stale after getting the first approval.

This adds a comment to the PR template with the goal of surfacing the policy and avoiding confusion.

@thiagoarrais
Copy link
Contributor Author

Shoot! Should've added [skip ci] to the commit.

@hzoo hzoo added the PR: Docs 📝 A type of pull request used for our changelog categories label Aug 9, 2019
@hzoo
Copy link
Member

hzoo commented Aug 9, 2019

I think I wrote some stuff before around this https://github.com/babel/babel/wiki/Maintaining-Babel#merging but yeah the general case is 2, unless it's more of a typo thing (mostly for the website),

I guess master is failing due to test fixtures (I assume related to data from compat type stuff)

Because, although two approvals is the general case, some PRs maybe merged with more or fewer approvals
@thiagoarrais
Copy link
Contributor Author

I wasn't aware of that documentation. Just added a qualifier to the proposal in light of that

@hzoo
Copy link
Member

hzoo commented Aug 12, 2019

Should be fine to merge if master is ok

@nicolo-ribaudo nicolo-ribaudo merged commit ee397ff into babel:master Aug 12, 2019
@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Nov 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Nov 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue PR: Docs 📝 A type of pull request used for our changelog categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants