Fix stale exit code in pr.yaml config fetch step#141
Merged
Chris-Wolfgang merged 1 commit intomainfrom Apr 25, 2026
Merged
Conversation
git cat-file -e sets $LASTEXITCODE=1 for missing files (e.g. BannedSymbols.txt). PowerShell propagates the stale exit code. Add explicit exit 0 at the end of the step. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
The PowerShell config fetch step fails with exit code 1 because
git cat-file -efor missing files (Directory.Build.props, BannedSymbols.txt) sets$LASTEXITCODE=1. PowerShell propagates this as the script's exit code even though the script handled it correctly.Adds
exit 0at the end of the step.This is blocking all PRs (#134, #135).
🤖 Generated with Claude Code