When disabled, git is read-only, when enabled my command allow-list is obsolete but i still want to double check before the commit goes through.
So you introduced the worst of both worlds. Could you maybe not introduce Junior/AI Slop?
Steps to Reproduce
have an actual working workflow with non-intrusive git commands allow list (git status/diff/add/log/show)
and then try to use this abomination of a “feature”…
Expected Behavior
instead of making git readonly which sounds a lot like an AI Slop shortcut (this isn’t your Browser, btw), maybe just forbid those intrusive git commands?
I get the issue. Right now it’s basically a binary choice. Either git is fully read-only, or everything is allowed without respecting your allowlist. It’s awkward when you want to allow status/diff/add, but still require approval for commit.
I’ve passed the feedback to the team. For now, the workaround is to keep “Allow Git Writes without Approval” turned off and manually approve git commit/git push, while adding other git commands to the allowlist. Those should still work for read operations.
yeah that would be nice if that could happen, then the whole post wouldn’t be necessary, but composer cant even ask for permission, every git commit is automatically prevented and composer identifies that as read-only.
Please tell me that your logical fallacies, obvious regurgitated misunderstandings here within your statement and the typical gpt conversation style is just a coincidence. Because your IDE’s supposedly “high” Opus 4.5 is also subpar and the combination of both would force me to re-evaluate using Cursor…
LLMs are a productivity tool not a replacement for responsibility.