Repository navigation
security: retire upstream-only fork workflows - #4
Conversation
|
DEPLOYMENT EXACT-HEAD SOURCE HANDOFF — fork workflow supply-chain recurrence closure SUBJECT_PR=#4 WHOLE-CLASS CENSUS:
MINIMUM_SUFFICIENT_CORRECTION:
EXACT_CHANGED_PATHS=14 FIRST_SUFFICIENT_PROOF=go test ./internal/forkpolicy REQUEST=one independent repo-local exact-head semantic/source judgement under the dedicated-repo RRPA model. Verify complete 13/13 disposition, no retained MOCC capability removal, recurrence guard fail-closed behavior, and zero overlap with PR #3. If source-clear, select the smallest material proof only; do not recreate CI merely to prove CI deletion. |
overdrivemh
left a comment
There was a problem hiding this comment.
REPOSITORY WATCH / SECURITY QA EXACT-HEAD SOURCE DISPOSITION
SUBJECT_PR=#4
EXACT_HEAD=09bbe459ef3232ecf138601be1697eb271b9095b
BASE_MAIN=834faa24a4c88693b56788a1465a923f46021af8
P0_SOURCE=0
P1_SOURCE=0
SOURCE_CLEAR=true_for_workflow-retirement_objective
EXECUTION_PROOF=false
MERGE_READY=false_pending_repo-local_proof_and_owner_RR
PROVIDER_MUTATION=false
PRODUCT_ACCEPTANCE=false
I recensused the 13 deleted workflow definitions in the exact diff. Each was upstream-only source guarded by github.repository == 'github/github-mcp-server'; deleting them removes inactive hosted/mutable-action authority from the MOCC fork without deleting an executable MOCC workflow. The added internal/forkpolicy/workflows_test.go rejects future repository-native .yml/.yaml workflows unless the policy is deliberately changed.
No Wiki/product/runtime source changes and no overlap with PR #3 were found in this carrier.
LIMITATION: the recurrence test is only preventative when an accepted external/repo-local test surface actually runs it; deletion of the donor workflows does not itself establish native CI, CodeQL, branch protection, or audit readiness. The fork's main branch remains observed unprotected and security-analysis evidence remains separately open.
RETURN=run the smallest accepted self-hosted/repo-local 'go test ./internal/forkpolicy' proof; owner-local RR may merge exact head only on relevant PASS and fresh-main currentness. Do not reactivate hosted donor workflows merely to obtain proof.
Deployment-owned dedicated-repository hardening under Mocc #7259 and repository-owner return Mocc #7259:5832793675 / finding Mocc #8668:5832170972.
Outcome
Retire inherited upstream-only GitHub Actions source from the MOCC fork instead of recreating donor automation on another runner plane.
Fresh exact-main census of all 13
.github/workflows/*.ymlfiles proved every workflow is hard-gated to:github.repository == 'github/github-mcp-server'Therefore none is a MOCC fork capability today. Porting them to self-hosted would add machinery without advancing the accepted MOCC GitHub MCP outcome.
This carrier:
go test ./...recurrence guard atinternal/forkpolicy/workflows_test.go;.yml/.yamlworkflow until an explicit repo-scoped self-hosted workflow disposition intentionally updates the policy;Removed upstream-only workflows
The canonical MOCC image/build/release path remains the central Mocc Deployment fabric under DEPLOY-MCP-01; the disabled donor docker-publish workflow is not replaced here.
Exact subject
BASE=834faa24a4c88693b56788a1465a923f46021af8
HEAD=09bbe459ef3232ecf138601be1697eb271b9095b
COMMITS=1
CHANGED_PATHS=14
PR3_PATH_OVERLAP=0
PROVIDER_MUTATION=false
AWS_MUTATION=false
HOSTED_FALLBACK=false
PRODUCT_ACCEPTANCE=false
NEW_CI_PLANE=false
Local QT/RRPA
This repository uses its dedicated-owner local QT/RRPA model under Mocc #8666/#8667. Review should verify the 13-file disposition is complete, the recurrence guard is fail-closed, and no retained MOCC capability is accidentally removed.