content: draft: Clarify branch protection in source track #1175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re: #1136
I'm trying to separate "branch protection" which is typically associated with SCP features from the property we want for the branches intended for consumption. I've also applied the SCS terminology we adopted in another PR.
The framing of how this can be accomplished is still a bit TBD, if we decide to adopt something like #1142 suggests, we could move the Git + GitHub/GitLab piece out? That's also where we could discuss server side pre-receive hooks etc.?