Ive been having issues where the pre commit git hook doesnt work anymore. i have a simple thing to bump some version numbers but it doesnt run automatically anymore.
Hey, thanks for the report. This looks like a known issue in 3.15.6. Commits made via the Source Control panel silently skip all git hooks like pre-commit, commit-msg, pre-push, and Husky. That shouldn’t happen, and it’s not something in your setup.
Just to double check, are you committing via the Source Control panel in Cursor? If yes, here are two workarounds until an update ships:
- Commit from the integrated terminal using
git commit. Hooks run normally there. - Or roll back to 3.14.27. Hooks work there too, confirmed by other users.
We’re tracking this, but there’s no exact timeline yet. There’s a thread you can follow for updates: Git hooks silently skipped for all Source Control operations since 3.15.6 — git extension forces `core.hooksPath=/dev/null`
Let me know if you’re not committing from the panel and you’re doing it another way, then we’ll take a separate look.
Just ran into this bug today after setting up pre-commit hooks for the first time and committing bad code to test through Cursor’s UI. I’m on version 3.16.17.
Hey @archon810, thanks for the report. This is the same issue we’re already tracking. Commits made via the Source Control panel silently skip git hooks like pre-commit, commit-msg, pre-push, and Husky. That shouldn’t happen, and it’s not related to your setup. It’s helpful to know it also reproduces on 3.16.17, I’ve passed it to the team.
For now, the workaround is to commit from the integrated terminal using git commit. Hooks run normally there.
You can follow updates in this thread: Git hooks silently skipped for all Source Control operations since 3.15.6 — git extension forces `core.hooksPath=/dev/null`. We’ll post there when we have news. No exact timeline yet.
@archon810 roll back to 3.14.27 version it is working fine
Updated to 3.17, still havving the same issue