style: apply the gopls quick fixes and fix their stale comments #644
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!644
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-631-apply-gopls-quick-fixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
gopls reported findings on main that have quick fixes. This applies all of them: tagged switches,
fmt.Fprintfin place ofWriteString(fmt.Sprintf(...)), splitWriteStringconcatenations, and three unused parameters (ctxingetConfigForURL,methodinenrichOwnerRepoError,errinfailResult).The removed parameters left two doc comments that still named them, in
failResultandenrichOwnerRepoError. I rewrote both.The Decision issues list change in #642 added one more split-
WriteStringfinding, ininternal/service/adr/adr.go. This applies that fix too.gopls check -severity=hintover the whole module now reports only the findings that #624 handles: the nil context ininternal/gitexec/env_test.goand the deprecated roots call ininternal/mcp/repoguard.go../scripts/gate.shpasses.Closes #631.
Closes #631