| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
don't have any experience with prek but interested in trying it
Sorry, something went wrong.
There was a problem hiding this comment.
seems to offer feature parity with pre-commit, can give it a shot
Sorry, something went wrong.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 3 total unresolved issues (including 2 from previous reviews).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit cabfaee. Configure here.
Sorry, something went wrong.
|
|
||
| ```bash | ||
| # Preferred for local backend changes: run only tests affected by your diff (fast) | ||
| make test-selective |
There was a problem hiding this comment.
fyi @rbro112 im removing this since it doesn't work for most people at the moment; agents should not attempt to do this
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
tools should run with minimal noise and only print relevant failures - it's less context pollution, less tokens and ultimately better signal for everyone (esp. coding agents)
all hooks have now been changed to be as quiet as possible, but pre-commit itself doesn't have the option to disable showing hook progress (see pre-commit/pre-commit#823), so i've replaced it with prek which is also faster
for interactive/manual use it is still unquiet because delayed silence is a little confusing - otherwise for coding agents and CI, it's quiet