You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As in my other project (click) I have configured pre-commit hooks that haven't allowed me to push to the repo if hooks were not successful. Actually I have literally 0 exprience in Go, but I believe this would be so beneficial. They could be also reflected in CIs.
The text was updated successfully, but these errors were encountered:
From my side it sounds good, I used git hooks before, they automate code quality tasks pretty well.
We could also ask the opinion of @dsonck92 on this, as he already setup for us golangci-lint, he must have great knowledge on this.
Heh, well, I'm all for it. One outstanding point regarding golangci-lint specifically, there is a bug somewhere with the caching system, which may produce false positives. This is mostly triggered by the ireturn linter. There is some discussion on whether the ireturn linter is actually something you want as there are use cases where you do want to return an interface.
As in my other project (click) I have configured pre-commit hooks that haven't allowed me to push to the repo if hooks were not successful. Actually I have literally 0 exprience in Go, but I believe this would be so beneficial. They could be also reflected in CIs.
The text was updated successfully, but these errors were encountered: