Fix Go linting errors in CI pipeline #195
Draft
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.
Resolves all golangci-lint errors blocking CI. The linter enforces strict error handling, modern Go syntax, and code quality standards across ~45 enabled linters.
Key Changes
Error Handling
validateErr,headErr,matchErr)commitMatchesFilter()to returnboolinstead of(bool, error)since error was always nilModern Go Syntax
0644→0o644http.NoBodyinstead ofnilfor GET requests without bodyfunc(a string, b string)→func(a, b string)Performance & Code Quality
TaskSystemConfigby pointer to reduce allocations"git"intoDefaultVCSTypeconstantlen(str) == 0withstr == ""for claritySecurity
0644to0600in report generatorExample
Two revive warnings remain about stuttering names (
task.TaskMatch,task.TaskSystem) but are intentionally not renamed to preserve API compatibility.Original prompt
This pull request was created from Copilot chat.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.