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.

Sign up for GitHub

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

Jump to bottom

Expand to include code review for spec changes #4

Open
foolip opened this issue Nov 8, 2019 · 2 comments
Open

Expand to include code review for spec changes #4

foolip opened this issue Nov 8, 2019 · 2 comments

Comments

@foolip
Copy link
Owner

foolip commented Nov 8, 2019

Context: https://groups.google.com/a/chromium.org/d/msg/blink-dev/rspPrQHfFkI/Qfv4OvzBCQAJ
@foolip
Copy link
Owner Author

foolip commented Nov 8, 2019

The implementation of this on the W3C side would be w3c/validate-repos#27.

@foolip
Copy link
Owner Author

foolip commented Nov 8, 2019

Beyond enforcing the branch protection, I'm a bit of a pessimist and think a tool to audit changes in repos would also be needed, because lots of editors will have admin access to their repos and can push to master directly without really noticing that they're overriding branch protection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@foolip and others