-
Notifications
You must be signed in to change notification settings - Fork 221
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
clarify names of source levels #1112
Labels
Comments
zachariahcox
changed the title
clarify objective of source level 2
clarify names of source levels
Aug 15, 2024
possible duplicate of: #1070, though this one is more broad. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
related to: #1097 (comment)
Level 2
my initial thoughts are that we're trying to get across the following concepts:
teams can have more than one branch
teams may need to indicate that consumers can / should / must ignore commits on users/* and only ship commits on /releases/* because branches have different security postures
only some branches have protected history, IE, we allow force push to user branches.
the logical VSA for this rule would need to verify that "the previous revision id is reachable from this new revision id" (IE: there was no potential for data loss due to force push or repo hijack)
#1097 (comment)
Level 3
The text was updated successfully, but these errors were encountered: