Commit Graph

10 Commits

Author SHA1 Message Date
privilegedescalation-ceo[bot] 6c0dcde8b5 Replace dual-approval with promotion gate workflow (#177)
New model: no review for dev PRs, QA gates uat, UAT gates main.
Replaces the old CTO+QA dual-approval check.

Co-authored-by: Chris Farhood <chris@farhood.org>
Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-05-11 21:37:00 +00:00
Chris Farhood f02d888d82 fix(ci): guard against null/missing PR number in dual-approval check
The workflow was failing on pull_request_review events when triggered by
non-PR actors (e.g. greptile-apps[bot] commenting). The dual-approval job
would attempt to call the reusable workflow with a null PR number,
causing the reusable workflow to fail since there was no valid PR to check.

Changes:
- Guard the PR number with explicit null check: [ -z "${PR_NUMBER}" ] || [ "${PR_NUMBER}" = "null" ]
- Add validation of the reviews response before processing
- Fix jq filter to handle null pipeline values explicitly

Fixes flapping Dual Approval (CTO + QA) checks across all plugin repos.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-05-05 10:21:27 +00:00
privilegedescalation-engineer[bot] 06e6784174 fix: skip dual approval check gracefully on dismissed reviews (#122)
* feat(release): add token permission pre-check

Detect missing write permissions early in the release pipeline rather
than failing late during git push with a cryptic 403 error (see PRI-348).

The new check-token-permissions job generates a GitHub App token and
attempts to create a test ref via the API. On 201 the token has write
permission (cleaned up immediately); on 403 the release job is skipped
with a clear error message. This saves CI time and provides actionable
diagnostics.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

* fix: skip dual approval check gracefully on dismissed reviews

When a pull_request_review event is dismissed, the PR context is null and
PR_NUMBER is empty. Instead of exiting with an error, exit 0 (skip) since
dismissed reviews are not approvals and do not affect the approval state.

Fixes PRI-314.

---------

Co-authored-by: Chris Farhood <chris@farhood.org>
Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-05-04 05:00:15 +00:00
Hugh Hackman d0635c4870 fix: make pr_number input optional in dual-approval-check
PR #81 adds pr_number as a required input, but the 5 calling
plugin repos don't yet pass this input. Change required: true
to required: false so the workflow_call can succeed without it,
while companion PRs are opened to add the input to each caller.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-03-25 13:04:52 +00:00
Hugh Hackman c31be7ef25 fix: add pr_number input to dual-approval-check workflow
The dual-approval workflow was not re-triggering on pull_request_review events because the shared workflow was using github.event.pull_request.number which is not available in workflow_call context.

This change adds a required pr_number input to the reusable workflow.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-03-25 12:51:52 +00:00
hugh-hackman[bot] 5a167e94ae fix(ci): use ubuntu-latest for dual-approval-check workflow
The dual-approval-check workflow only makes GitHub API calls — it does
not need cluster access or any self-hosted tooling. Using the
self-hosted runner (runners-privilegedescalation) was triggering
GitHub's self-hosted runner approval requirement for workflows run by
actors with authorAssociation NONE (e.g. privilegedescalation-qa/cto
bots), causing action_required conclusions with 0 jobs executed.

Switching to ubuntu-latest eliminates the approval gate and frees
self-hosted runner capacity for actual CI builds.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-03-24 21:54:04 +00:00
Hugh Hackman cede9322dc fix(ci): match [bot] suffix in dual-approval-check reviewer usernames
GitHub App reviews are submitted as `privilegedescalation-cto[bot]`
and `privilegedescalation-qa[bot]`, not the bare usernames used in the
workflow defaults. The jq filter now accepts both the plain username and
the `[bot]`-suffixed form, so the check passes regardless of whether the
review was submitted via the GitHub App or a regular account.

Fixes: https://github.com/privilegedescalation/.github/issues/51

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-03-22 05:12:50 +00:00
Hugh Hackman 950af300bf fix: replace gh api with curl in dual-approval-check workflow
The gh CLI is not installed on the self-hosted ARC runners
(runners-privilegedescalation). Replace the gh api call with
curl + GitHub token, which is available on all runners.

Fixes: https://github.com/privilegedescalation/.github/issues/50
Unblocks: headlamp-polaris-plugin PR #98 and v1.0.0 release pipeline
2026-03-22 04:45:20 +00:00
Hugh Hackman 1c5eb52490 fix(ci): check last review state per user in dual-approval workflow
Previously the jq logic checked if *any* review from CTO/QA had
state == APPROVED. This allowed a PR to pass dual-approval even if
the reviewer subsequently requested changes — because the earlier
approval was still in the review history.

Fix: filter reviews by user, take the last one, and check its state.
This ensures a CHANGES_REQUESTED review after an approval correctly
blocks the check.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-03-22 00:11:01 +00:00
Hugh Hackman fbb4dfcfc3 ci: add reusable dual-approval-check workflow
Adds a shared reusable workflow that plugin repos can call to enforce
the dual CTO+QA approval policy as a GitHub required status check.

The workflow queries the GitHub API for PR reviews and fails unless
both privilegedescalation-cto and privilegedescalation-qa have approved.
Triggered via pull_request and pull_request_review events in calling
repos, producing a clear "Dual Approval (CTO + QA)" status check.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-03-21 23:54:57 +00:00