Repository navigation
docs: require independent change review #15530
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
Open
austinywang
wants to merge
3
commits into
main
Choose a base branch
from
15527-compliance-review-controls
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| # Change management evidence | ||
|
|
||
| cmux changes are merged through GitHub pull requests. The default branch is | ||
| protected by a repository ruleset that requires at least one approving review | ||
| before a pull request can merge. Pull-request authors cannot approve their own | ||
| changes. | ||
|
|
||
| The approval must come from a contributor other than the pull-request author | ||
| and must be recorded in GitHub before merge. Reviewers are responsible for | ||
| checking the change, its tests, and the stated verification evidence. Changes | ||
| to publish-critical or secret-touching paths also require the matching | ||
| CODEOWNER review. | ||
|
|
||
| ## Exceptions | ||
|
|
||
| Historical or incident exceptions are recorded when the normal reviewer path | ||
| was unavailable or would have created an incident response delay. The pull | ||
| request must record all of the following in its Summary or Testing section: | ||
|
|
||
| - the concrete reason an independent review was unavailable; | ||
| - the person who approved the exception; and | ||
| - the verification or release review that compensates for the missing review. | ||
|
|
||
| The linked repositories enforce the review gate through their GitHub branch | ||
| protection configuration; the live settings and their Vanta evidence are | ||
| recorded in [issue #15527](https://github.com/manaflow-ai/cmux/issues/15527). | ||
| This document describes the process and does not define or override those | ||
| repository settings. An exception note does not waive the gate or authorize an | ||
| author or maintainer to merge without the required review. If the normal | ||
| reviewer path is unavailable, hold the merge until an independent reviewer is | ||
| available. For a historical or separately approved incident exception that | ||
| already merged outside the gate, attach the exception to the pull request and | ||
| release record so an auditor can distinguish it from an unreviewed change. A | ||
| release review does not retroactively turn an old pull request into an | ||
| independently approved pull request; historical exceptions remain identified as | ||
| exceptions. | ||
|
|
||
| This document describes the engineering change-management process. It is | ||
| operational evidence for the applicable compliance controls and is not a claim | ||
| of certification or regulatory approval. | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: manaflow-ai/cmux
Length of output: 40935
🏁 Script executed:
Repository: manaflow-ai/cmux
Length of output: 7815
🏁 Script executed:
Repository: manaflow-ai/cmux
Length of output: 1970
🏁 Script executed:
Repository: manaflow-ai/cmux
Length of output: 6440
Configure the GitHub review gate before documenting it as active.
The active ruleset for the default branch requires only status checks, deletion protection, and non-fast-forward protection. It does not require an independent approval or CODEOWNER approval. A pull request that passes those checks can merge without the review described here.
Configure the GitHub ruleset. Changing this document cannot enforce the policy.
🤖 Prompt for AI Agents