SRE-737: Remove dismiss-stale-approvals preflight in favor of GitHub-native#70
Conversation
…native Retire the custom dismiss-stale-approvals reusable workflow and its range-diff composite action. Stale-approval dismissal moves to the GitHub-native dismiss_stale_reviews_on_push, configured via branch protection / org ruleset. Consumer repositories drop their stale-approvals job in follow-up PRs; they are SHA-pinned to the previous commit, so their preflight stays green until updated.
PR SummaryMedium Risk Overview The PR deletes Rollout note: other repos that SHA-pin this workflow keep the old preflight until they remove their Reviewed by Cursor Bugbot for commit 6769e75. Bugbot is set up for automated code reviews on this repo. Configure here. |
🤖 Augment PR SummarySummary: This PR retires the custom “dismiss stale approvals” preflight mechanism in favor of GitHub’s native stale-review dismissal (configured via branch protection / org rulesets). Changes:
Technical Notes:
🤖 Was this summary useful? React with 👍 or 👎 |
|
@copilot fix conflicts |
…om-dismiss-stale-approvals-preflight-switch-to # Conflicts: # .github/actions/dismiss-stale-approvals/action.yml # .github/workflows/preflight-stale-approvals.yml
Merged |
Purpose
Retire the custom dismiss-stale-approvals preflight in favor of GitHub-native stale-approval dismissal (
dismiss_stale_reviews_on_push, configured via branch protection / org ruleset).The custom range-diff action is smarter (only dismisses on real diff changes) but unreliable in practice: it dismisses approvals after merge (Vanta compliance noise), rebases fail opaquely, and the maintenance cost is too high. GitHub-native stack support is expected to make the custom logic moot anyway.
What does this change?
Deletes the reusable workflow and its composite action:
.github/workflows/preflight-stale-approvals.yml.github/actions/dismiss-stale-approvals/(8 files)No references to these remain in this repo.
Rollout
.github-first per the plan. Consumers are SHA-pinned to the previous commit, so their preflight stays green until they drop thestale-approvalsjob in follow-up PRs. Branch protection is being switched to GitHub-native dismissal in parallel.Related links