fix unable to use CLI in corporate proxy setting#451
Merged
jakecoffman merged 1 commit intomainfrom May 30, 2025
Merged
Conversation
jakecoffman
force-pushed
the
set-proxy-headers-in-proxy
branch
from
497d2da to
611a540
Compare
JamieMagee
approved these changes
May 30, 2025
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
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.
It's common in corporate settings to have a proxy setup which routes calls through a corporate proxy. The dependabot-action handles that here, but the CLI didn't have these environment variables set yet.
From a CLI perspective it makes sense to simply pass these along rather than make a dedicated flag for it as it should then "just work."
HTTPS_PROXYnot available in containers for accessing internet locations #450