Skip to content

Comments

language/go: add golangci-lint for extra diagnostics#1376

Merged
horriblename merged 1 commit intoNotAShelf:mainfrom
snoweuph:feature/go
Feb 1, 2026
Merged

language/go: add golangci-lint for extra diagnostics#1376
horriblename merged 1 commit intoNotAShelf:mainfrom
snoweuph:feature/go

Conversation

@snoweuph
Copy link
Contributor

@snoweuph snoweuph commented Jan 30, 2026

Adds golanci-lint for more diagnostics in go.

works just fine with severity mapping of the config file:
image
image
image

Sanity Checking

  • I have updated the changelog as per my changes
  • I have tested, and self-reviewed my code
  • My changes fit guidelines found in hacking nvf
  • Style and consistency
    • I ran Alejandra to format my code (nix fmt)
    • My code conforms to the editorconfig configuration of the project
    • My changes are consistent with the rest of the codebase
  • If new changes are particularly complex:
    • My code includes comments in particularly complex areas
    • I have added a section in the manual
    • (For breaking changes) I have included a migration guide
  • Package(s) built:
    • .#nix (default package)
    • .#maximal
    • .#docs-html (manual, must build)
    • .#docs-linkcheck (optional, please build if adding links)
  • Tested on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin

Add a 👍 reaction to pull requests you find important.

github-actions bot pushed a commit that referenced this pull request Jan 31, 2026
@github-actions
Copy link

github-actions bot commented Jan 31, 2026

🚀 Live preview deployed from fde1338

View it here:

Debug Information

Triggered by: snoweuph

HEAD at: feature/go

Reruns: 2001

@snoweuph
Copy link
Contributor Author

I plan on adding a few more common go diagnostic tools in followup MRs.
Is there a timeline, when the 0.9 release will be cut?
I would like to get them all into it :D

github-actions bot pushed a commit that referenced this pull request Jan 31, 2026
@snoweuph
Copy link
Contributor Author

🚀 Live preview deployed from fde1338

View it here:
Debug Information

image

@horriblename
Copy link
Collaborator

Is there a timeline, when the 0.9 release will be cut?

not anytime soon, we usually only make a release when we have breaking changes, and we don't have any planned at the moment (unless @NotAShelf has a release schedule he didn't tell me about)

github-actions bot pushed a commit that referenced this pull request Jan 31, 2026
@snoweuph snoweuph requested a review from horriblename January 31, 2026 02:19
github-actions bot pushed a commit that referenced this pull request Jan 31, 2026
github-actions bot pushed a commit that referenced this pull request Jan 31, 2026
@snoweuph snoweuph force-pushed the feature/go branch 2 times, most recently from 1a3e26d to 03bc637 Compare January 31, 2026 13:56
@snoweuph snoweuph requested a review from horriblename January 31, 2026 13:57
github-actions bot pushed a commit that referenced this pull request Jan 31, 2026
@snoweuph
Copy link
Contributor Author

i gonna test the changes i id again, just to be sure

@snoweuph
Copy link
Contributor Author

snoweuph commented Jan 31, 2026

still works as expected.
@horriblename ready for re-review

@snoweuph
Copy link
Contributor Author

this is a great learning experince for me :D

adding a few of the other missing diags from my list, should go much faster, in the future :D

github-actions bot pushed a commit that referenced this pull request Jan 31, 2026
Copy link
Collaborator

@horriblename horriblename left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@horriblename horriblename enabled auto-merge (squash) February 1, 2026 03:03
@horriblename horriblename merged commit 8aae700 into NotAShelf:main Feb 1, 2026
14 checks passed
@snoweuph snoweuph deleted the feature/go branch February 1, 2026 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants