K<p>My golang knowledge is pretty basic. I had to do some updates to a product at work, and it was pretty easy and straight forward. Actually quite fun. Just to learn more golang, I started working on a cli-tool for my Niri setup, and it's actually pretty usable already. <br>I just want to polish it and clean up the code a bit more before publishing it. Also, since I'm not that good at the language yet, I'm totally not sure if I even do things correctly or the 'golang' way.</p><p>Any tips on which pre-commit hooks people usually use? I found one repo that has pretty much everything, but I always welcome alternatives.<br>I was also thinking about go-semantic-release to handle the package releases.</p><p>I know, this is probably quite overkill for a simple project, but hey, I like to learn and do things correctly! </p><p><a href="https://social.linux.pizza/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>golang</span></a> <a href="https://social.linux.pizza/tags/go" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>go</span></a> <a href="https://social.linux.pizza/tags/niri" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>niri</span></a> <a href="https://social.linux.pizza/tags/PreCommit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PreCommit</span></a> <a href="https://social.linux.pizza/tags/CliTools" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CliTools</span></a> <a href="https://social.linux.pizza/tags/learning" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>learning</span></a></p>