Repository navigation
Fix consistent linter findings for issue #16 - #36
Merged
Merged
Conversation
pavetok
marked this pull request as ready for review
October 11, 2026 20:10
pavetok
enabled auto-merge
October 11, 2026 20:20
pavetok
disabled auto-merge
October 11, 2026 20:21
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
1 participant
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.
Summary
Addresses the three
linter:consistentfindings reported in orglang/go-workspace#16:The current
mainbranch already pinshonnef.co/go/toolsatv0.8.1andgolang.org/x/toolsatv0.51.0, so this PR does not change those versions. I could not execute Taskfile commands in the GitHub-hosted environment; CI/local verification is still needed for both acceptance commands, including triage of any newly surfaced staticcheck findings.