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

Add "protected" property to branches #2181

Closed
ozkatz opened this issue Jun 29, 2021 · 0 comments
Closed

Add "protected" property to branches #2181

ozkatz opened this issue Jun 29, 2021 · 0 comments
Assignees
Labels
area/hooks improvements or additions to the hooks subsystem roadmap epic

Comments

@ozkatz
Copy link
Collaborator

ozkatz commented Jun 29, 2021

Allow some branches to be configured as "protected". When configured, these branches cannot be directly written to (i.e. technically, will not have a staging area). These branches can only receive changes by being merged into.

This is useful when designing a CI/CD pipeline: assuming data consumers read from "main", we can configure pre-merge hooks to run and validate any new change being applied. This gives a strong guarantee to readers about the validity and quality of anything they see on main.

@nopcoder nopcoder added the area/hooks improvements or additions to the hooks subsystem label Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/hooks improvements or additions to the hooks subsystem roadmap epic
Projects
None yet
Development

No branches or pull requests

3 participants