Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
$expansion fix here is correct and worth keeping. In a Make recipe$Hexpands the (undefined) Make variableHto empty, leaving the literalOMEBREW_NO_AUTO_UPDATE=1 brew upgrade …. That stray token never sets the env var, so everymake lintwas actually triggering a full Homebrew auto-update. Dropping the$passes the assignment through to the shell. Good catch. 👍One caveat now that commit
c2f232b3reverted back tobrew upgrade: on a machine that has never installed golangci-lint,brew upgrade golangci-lintstill fails withError: golangci-lint not installed— which is exactly the fresh-machine scenario in #1038. So with the current diff this target is not idempotent on a clean machine.If keeping
brew upgradeis the intended scope, consider making it self-bootstrapping without losing the upgrade behaviour:Re: @gsavage's questions — with
brew upgradekept, the linter does stay current (mechanism for keeping it up-to-date), and it's unpinned, which matches CI'sgolangci-lint-actionatversion: latest. Pinning to a specific version would be a deliberate separate change if you want local == a fixed CI version.