Add support for CLI global flag configurations #577
Merged
Conversation
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
EhabY
commented
Sep 2, 2025
EhabY
commented
Sep 2, 2025
EhabY
commented
Sep 2, 2025
EhabY
force-pushed
the
support-cli-global-flags
branch
from
1ad3a20 to
08a2dc3
Compare
EhabY
commented
Sep 8, 2025
code-asher
approved these changes
Sep 8, 2025
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.
#500
Add the settings
coder.globalFlagsto add global flags to allcoderCLI invocations in VS Code. However, since we already havecoder.headerCommandwhich sets the--header-command, this setting takes precedence over manually entered--header-commandin the global flags settings. Same thing happens for the--global-configthough that one is set internally and not through a setting