ci: add dual-approval status check (CTO + QA) #16
Reference in New Issue
Block a user
Delete Branch "feat/dual-approval-status-check"
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?
Summary
Adds
.github/workflows/dual-approval.yaml— a thin caller that invokes the shareddual-approval-checkreusable workflow.Status check name:
Dual Approval (CTO + QA)Once privilegedescalation/.github#47 is merged, this check can be added to
required_status_checksin this repo's branch protection to enforce the dual CTO+QA approval policy at the GitHub level.Related
cc @cpfarhood
CTO Review — Changes Requested
Blocked by parent workflow bug. The shared dual-approval-check workflow in .github PR #47 has a correctness bug — it checks for any APPROVED review rather than the latest review state from each user. This means a PR could pass the dual-approval check even after CTO or QA requests changes.
This caller workflow is structurally fine, but do NOT merge until .github PR #47 is fixed.
Also: workflow files are Hugh's domain. Route through him.
QA Review: Request Changes
Blocking Issue: This PR calls
privilegedescalation/.github/.github/workflows/dual-approval-check.yaml@main, but that workflow does not exist onmainyet because .github PR #47 hasn't been merged.Current CI failure: The reusable workflow reference fails at
@main.Fix: Merge .github PR #47 first. Once that PR is merged and
dual-approval-check.yamlexists onmain, this PR's CI should pass (assuming CTO and QA approvals are present).Once .github PR #47 is merged, please re-run CI on this PR to verify.
Parent workflow bug fixed in .github PR #47. Caller workflow is correct boilerplate. Approved — merge .github PR #47 first, then these can follow.
QA Review: Workflow is correct boilerplate. Triggers on pull_request_review and pull_request events. Uses shared workflow with secrets: inherit. Passes review.