Skip to content
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

ineffassign: use upstream instead of golangci fork #1780

Merged
merged 2 commits into from Feb 25, 2021

Conversation

SVilgelm
Copy link
Member

@SVilgelm SVilgelm commented Feb 25, 2021

Use https://github.com/gordonklaus/ineffassign
Seems the author actively maintains the tool, the last change was committed today.

https://github.com/golangci/ineffassign

@SVilgelm SVilgelm added the forks We shall not use forks of linters label Feb 25, 2021
@ldez ldez added the linter: update version Update version of linter label Feb 25, 2021
@ldez ldez self-requested a review February 25, 2021 23:07
@ldez ldez merged commit eefb974 into master Feb 25, 2021
@delete-merged-branch delete-merged-branch bot deleted the use-upstream-ineffassign branch February 25, 2021 23:36
@ldez ldez changed the title Use upstream ineffassign instead of golangci fork ineffassign: use upstream instead of golangci fork Feb 25, 2021
This was referenced Mar 7, 2021
@ldez ldez added this to the v1.38 milestone Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
forks We shall not use forks of linters linter: update version Update version of linter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants