繁體中文

問題修復

工作階段運行已久時,唯讀 Git 指令不再誤跳授權詢問

當你長時間開啟工作階段(從開啟工具到結束對話的完整操作過程)處理專案時,如果只想查閱檔案紀錄,最怕流程莫名被打斷。

在先前的 2.1.269 版本中,工具就出現了這項令人困擾的退步問題。當時只要你在 Bash(在黑底白字視窗裡輸入文字指令的運作環境)中持續操作了一段時間,原本完全不更動任何檔案的 Git 唯讀指令,就會出乎意料地彈出確認提示,反覆向你要求授權。特別是像 Git 這種用來追蹤檔案修改歷程的工具,其查詢狀態或檢視歷史的指令純粹只是讀取資料,本就不該頻繁索取權限。這項問題現在已經修好,往後即使工作階段持續運行,各類唯讀指令也能順暢完成,不再出現多餘的授權詢問來打斷你的思路。

English

BUGFIX

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.

原始 CHANGELOG

Original changelog工作階段運行已久時,唯讀 Git 指令不再誤跳授權詢問
Fixed read-only git commands in Bash unexpectedly asking for permission after a session had been running for a while (regression in 2.1.269)