4 ms·
Having never used this specific product I can't makes claims about any of its functionality, but what I have found is the gap between what one _can_ do, and wha
by dkhenry 11y ago
Having never used this specific product I can't makes claims about any of its functionality, but what I have found is the gap between what one _can_ do, and what people _do_ is very very large. Yeah you can implement all this yourself using pre commit hooks, but do you ? Right now you could pay a little money and vastly improve the quality of your code base. There is value to be added by getting a packaged version of something and having it just work.
- ThePhysicist 11y agoGood point! When asking developers about their use of static code analysis to ensure code quality we found that most development teams use such tools only sporadically or not at all, and just very few teams have a systematic process or set of guidelines for ensuring code quality throughout all of their projects. So while some technologies already exist for this, we definitely think that there's room for more.
- gknoy 11y agoI'm not a fan of pre-commit hooks (as I'd rather write it, lint it, fix-rebase-it), but I love having a CI suite that includes the linting tests that our team has agreed on. It lets me code away and lint things when I'm ready to make my pull requests.
- jquast 11y agoagreed, git hooks are a terrible place, they can actually impede progress and can also be skipped/disabled/never installed in the first place. The time for rejecting a build for linting is at time of merge to trunk/next release, which a good CI should already have checked.
- ThePhysicist 11y agoyeah that's the workflow we have in mind as well: -make changes in a feature branch -have the linter run on each commit to see if there are problems -when you make a pull request, check the code again and comment on the PR if there are any problems.