-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dont override golangci go #2116
Conversation
Signed-off-by: Kristoffer Dalby <[email protected]>
Note Currently processing new changes in this PR. This may take a few minutes, please wait... Files selected for processing (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
golangci-lint = prev.golangci-lint.override { | ||
buildGoModule = buildGo; | ||
}; | ||
# Upstream does not override buildGoModule properly, |
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.
We want to use the latest go for golangci-lint anyway regardless of what version headscale is using.
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.
Yes, it was building with 1.22 upstream, then I set it to 1.23, but upstream changed to take buildGo123Module
instead which made it a bit awkward.
golangci-lint gets sad when you use the wrong go version to build it, so it was to make it use the same as ours.
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.
It gets sad, if you use a newer go version than it was built with. Building golangci-lint with a newer version than later is being used, is fine.
No description provided.