Skip to content

Fix CleanUpStalePRChecks to handle UNKNOWN mergeable state#8165

Draft
Copilot wants to merge 1 commit into
mainfrom
copilot/fix-stale-pr-status-checks
Draft

Fix CleanUpStalePRChecks to handle UNKNOWN mergeable state#8165
Copilot wants to merge 1 commit into
mainfrom
copilot/fix-stale-pr-status-checks

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 15, 2026

Problem

The "Clean Up Stale PR Status Checks" workflow only cleans up stale PR builds when the PR's mergeable state is MERGEABLE. However, GitHub sometimes reports the mergeable state as UNKNOWN (when it hasn't computed mergeability yet), causing those PRs to be skipped and their stale status checks to remain.

Fix

Changed the condition to only skip PRs with CONFLICTING state (actual merge conflicts that need manual resolution). PRs in both MERGEABLE and UNKNOWN states are now processed for stale check cleanup.

Changes

  • .github/actions/CleanUpStalePRChecks/action.ps1: Replaced $pr.mergeable -ne "MERGEABLE" check with $pr.mergeable -eq "CONFLICTING" to allow processing of PRs in UNKNOWN state.

Previously, the workflow only processed PRs in MERGEABLE state,
skipping PRs where GitHub reports the mergeable state as UNKNOWN
(which happens when mergeability hasn't been computed yet).

Now the workflow only skips PRs with CONFLICTING state (actual
merge conflicts), and processes PRs in both MERGEABLE and UNKNOWN
states.

Agent-Logs-Url: https://github.com/microsoft/BCApps/sessions/9253504e-b5c0-4cd7-90a0-cf30c897fbe3

Co-authored-by: mazhelez <43066499+mazhelez@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants