Read-only Git commands no longer mistakenly prompt for permission during long-running sessions
When you keep a session open for a long time to work on a project and simply want to inspect file history, having your workflow randomly interrupted is frustrating.
In the previous 2.1.269 release, the tool suffered from this frustrating regression. Back then, after operating for a while in Bash, read-only Git commands that modify no files at all would unexpectedly trigger confirmation prompts and repeatedly demand permission. Especially for a tool like Git used to track file modification history, commands that inspect status or view history purely read data and should never demand permissions so frequently. This issue has now been resolved; going forward, even when a session runs continuously, various read-only commands complete smoothly without unnecessary permission prompts interrupting your flow.