fix(dogfood/coder): disable gh terminal color probes#26114
Open
johnstcn wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Newer GitHub CLI versions probe terminal colors before interactive prompts, which can leave OSC responses in dogfood web terminal stdin and break
gh auth login.Default
NO_COLOR=1inside the dogfood/usr/local/bin/ghwrappers when callers have not set it themselves. This avoids the color probe without pinning or downgradinggh, and keeps the existing Coder external-auth wrapper behavior intact.Refs ENG-2842.
Coder Agents disclosure
This PR was generated by Coder Agents on behalf of @johnstcn.