ci(audit-force-merge): fan §SOP-6 force-merge audit to molecule-core #150
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fan/audit-force-merge"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Mirrors the canonical workflow shipped on
internal#120+internal#122. Same shape:pull_request_targetonclosedREQUIRED_CHECKSenv declares both molecule-core/main protected contexts:sop-tier-check / tier-check (pull_request)Secret scan / Scan diff for credential-shaped strings (pull_request)Mirror against branch protection if either is added/removed (per
feedback_least_privilege_via_workflow_env).Verified on internal
Synthetic force-merge of
internal#123emitted the structured event with all expected fields. Loki query:Returned:
{event_type:"incident.force_merge", pr:123, merged_by:"claude-ceo-assistant", failed_checks:["sop-tier-check / tier-check (pull_request)=failure"]}Tier
tier:low — CI workflow only, no platform code path.
Approved — direct port of the verified internal workflow. REQUIRED_CHECKS env correctly lists both molecule-core/main protected contexts.
New commits pushed, approval review dismissed automatically according to repository settings
Re-approving after secret-scan port push. The .gitea/ port mirrors the .github/ logic, drops merge_group + workflow_call (Gitea-incompatible), and keeps the same job+step names so the status-check context matches branch protection.