feat: fall back to CODER_HEADER_COMMAND environment variable if not set #160
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
JoshVee
commented
Nov 3, 2023
kylecarbs
approved these changes
Nov 3, 2023
JoshVee
commented
Nov 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
The Coder CLI supports using the
CODER_HEADER_COMMANDenvironment variable to configure the custom header command.Intent
This PR adds the ability to fall back to this environment variable if the
coder.headerCommandconfiguration has not explicitly been set.This ensures that users who have already set up their environment to use the
coderCLI, can seamlessly switch to using the VSCode extension.