Repository navigation
fix(apply-repo-settings): surface full API error body via step summary - #63
Merged
Merged
Conversation
GitHub truncates the single-line ::error:: annotation at the first newline.
On a JSON error body, that's the first '{' — losing every useful field
('message', 'errors[]', etc.). Now:
- Compact the body via jq before emitting the annotation so the full
object survives.
- Also append the pretty-printed body to GITHUB_STEP_SUMMARY so the full
failure is visible on the job page and via /actions/jobs/{id} →
output.summary.
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
Debugging the apply-repo-settings runs (post-yq-fix) is blocked because the HTTP 422 body is truncated at the first newline (the opening '{' of the JSON) in the GitHub annotation. The actual error message and field list are unreachable.
Fix:
Test plan
🤖