-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Upgrade golangci-lint to v1.64.5 #33654
Conversation
2720749
to
5c0fc1d
Compare
5c0fc1d
to
4738feb
Compare
I recommend also making it more strict and enable the default-disabled options: linter-settings:
usetesting:
os-setenv: true
os-temp-dir: true |
IIRC they are enabled by default, that's why it needs this change: 6a5111d |
Hmm, I see that If there are too many changes, then leave it to a new PR Update: now And applied suggestions from #33655 (comment) for the Makefile |
The docs say it's disabled by default. Is it a docs bug? # Enable/disable `os.Setenv()` detections.
# Default: false
os-setenv: true |
I think it is. The rule triggered for me but I figured that all those context changes + loop are big enough for a PR. |
(Update: hmm, maybe https://golangci-lint.run/usage/linters/#usetesting Also see the doc screenshot in #33654 (comment) |
Opened ldez/usetesting#7 |
* giteaofficial/main: Fix omitempty bug (go-gitea#33663) Upgrade golangci-lint to v1.64.5 (go-gitea#33654) Fix mCaptcha bug (go-gitea#33659) Update Go dependencies (skip blevesearch, meilisearch) (go-gitea#33655) Use test context in tests and new loop system in benchmarks (go-gitea#33648) Add missed changelogs (go-gitea#33649) [skip ci] Updated translations via Crowdin git graph: don't show detached commits (go-gitea#33645)
Use
usetesting
instead of deprecatedtenv
.