fix(gh): report all forced terminal metadata degradation - #413
Merged
codeforester merged 1 commit intoSep 3, 2026
Conversation
codeforester
deleted the
bug/408-20260904-lib-gh-sh-follow-up-to-394-forced-terminal-env-warning-misse
branch
September 3, 2026 20:50
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
Report forced terminal rendering that disables structured GitHub API retry metadata on every affected path, including explicit
--includecallers and mutations.Issue
Fixes #408
Validation
bats lib/bash/gh/tests/lib_gh.bats(72/72)env -u BASE_HOME BASE_CACHE_DIR=/private/tmp/base-bash-libs-408 ./tests/validate.sh(616/616 plus all repository contracts)Compatibility and security
The existing fail-closed metadata behavior is preserved; this centralizes detection and adds diagnostics without exposing request data.