Repository navigation
feat(governance): align twin content and detect drift - #8
Conversation
|
@codex review |
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
The account paying for this security review has reached its Codex usage limits. The payer can check the Codex usage dashboard. For personal accounts, using credits requires enabling “Use credits for security reviews” in Code review settings. If you do not manage the paying account, contact this repository's admins. |
1 similar comment
|
The account paying for this security review has reached its Codex usage limits. The payer can check the Codex usage dashboard. For personal accounts, using credits requires enabling “Use credits for security reviews” in Code review settings. If you do not manage the paying account, contact this repository's admins. |
|
@codex review |
|
The account paying for this security review has reached its Codex usage limits. The payer can check the Codex usage dashboard. For personal accounts, using credits requires enabling “Use credits for security reviews” in Code review settings. If you do not manage the paying account, contact this repository's admins. |
|
Codex Review: Didn't find any major issues. What shall we delve into next? Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Problem
The three twin governance repositories drifted. This repository was missing the reviewer configuration that
QuantStrategyLab/.githubcarries, its README pointed at adocs/private-repositories.mdthat does not exist here, it still tracked a Python bytecode cache, and no repository declared or verified a shared revision.Changes
pr-governance/with the shared revision: reviewer configuration inmain.cjs,test-main.cjsandtemplates/risk-gate.yml, plus one README text for all three organizations.pr-governance/scripts/__pycache__/secret_scan.cpython-313.pyc.VERSION(3, the policy revision).pr-governance/scripts/check-twin-drift.shand.github/workflows/governance-drift.yml: weekly and on demand, they comparepr-governance/andVERSIONacrossPigbibi/governance,GdeiAssistant/.githubandQuantStrategyLab/.github.The matching change is open in
Pigbibi/governance#10andQuantStrategyLab/.github; the drift workflow reports success once all three merge.Validation
node --test pr-governance/scripts/test-*.cjs— 164 tests pass.git ls-files pr-governance | grep __pycache__returns nothing after this change.sh pr-governance/scripts/check-twin-drift.shafter the sibling merges.Risk and compatibility
The drift workflow is advisory (weekly schedule and manual dispatch); it does not gate pull requests. No gate behavior changes: the scripts are byte-identical to the QuantStrategyLab copy that already runs in production.
AI assistance
What changed
This repository now runs the same reviewed governance engine as the other two organizations and can prove it has not drifted.