Fix Evergreen workflow: exit 0 when no PRs need attention - #122
Merged
Conversation
The pre-flight step was using sys.exit(1) for "no work to do" cases, which marked the workflow as failed and triggered spurious failure issues. Changed to sys.exit(0) for the normal "no open PRs" and "no PRs need attention" paths. Added noop instruction to the agent prompt so it handles the null selection gracefully. Agent-Logs-Url: https://github.com/githubnext/tsessebe/sessions/4c6e25d0-358d-4732-b45a-4ed8a1e3ecb8 Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>
mrjf
marked this pull request as ready for review
April 12, 2026 12:04
Copilot
AI
changed the title
[WIP] Debug workflow failure for Evergreen PR Health Keeper
Fix Evergreen workflow: exit 0 when no PRs need attention
Apr 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Evergreen pre-flight step used
sys.exit(1)for "no PRs need attention" — a normal state on a 5-minute schedule. The framework treated this as a job failure and created spurious issues every run.sys.exit(1)→sys.exit(0)for the two "nothing to do" paths (no open PRs, all PRs healthy). Keptsys.exit(1)for actual errors (forced PR not found).gh aw compile.