1 year ago

At Tighten, we’ve long believed that individual programmers shouldn’t waste their time worrying about code formatting. Early in our history, Tighten alum Adam Wathan saw Matt wasting time reviewing code style issues and built an entire CI tool, Nitpick, in large part responding to that waste. But as our opinions about how to write code—especially in Laravel—have grown, it’s been harder and harder to find the right tooling to enforce all of our code styles.

Linting will report issues but won’t make any changes to your codebase, and fixing will report and fix issues found.

To run Duster only on files that have uncommitted changes according to Git, you can use the --dirty option: ./vendor/bin/duster lint --dirty #or ./vendor/bin/duster fix --dirty