Adding postcommit hooks without asking is intrusive
complete
Nick Omeyer
complete
Hey Paul Lewis, we've removed the post-commit hook feature from both VSCode & JetBrains IDEs.
As soon as you update your extensions, they should stop creating post commit hooks for new repos you open up.
Unfortunately this release won't clean up existing post-commit hooks that have been created. We chose not to implement this because of the potential messiness if you had other post-commit hooks on these repos. You can remove them manually by finding & editing the
.git/hooks/post-commit
file(s) in your repo(s).Sorry for the inconvenience & thanks for your feedback! 🙏
Nick Omeyer
in progress
We'll be removing the post-commit hook feature this week. It didn't work out the way we expected it to – instead of being a useful reminder to track tech debt it's more of an annoyance. Thanks for flagging this Paul.
Nick Omeyer
under review
Thanks for letting us know Paul – that makes sense and apologies for the disruption caused. We're planning our next sprint tomorrow and this will most likely make it in.
You might know this already, but just in case – for now you can switch off this behaviour in the extension's settings, and clean up the mess we've created by finding & editing the
.git/hooks/post-commit
file(s) in your repo(s) 😬