GitHub CLI 2.86.0

現在你想在終端機使用 Copilot CLI（讓你透過文字指令使用 Copilot 的工具）時，可以直接輸入 gh copilot；電腦尚未安裝它就會先詢問你是否安裝，裝好後接著啟動。若你已經知道要交代什麼，也能在後面接上參數與旗標，gh 會原封不動轉交給 Copilot CLI 執行。這不是讓 Copilot 多了新本事，而是把原本要另外找安裝程式、再切換指令的兩段路接起來，像在車站同一個窗口買票後直接上車。

現在你要清理某個 ref（Git 用來指向分支或版本的名稱）留下的快取（把先前結果暫存、下次直接使用的資料）時，gh cache delete 可以一次刪掉該 ref 的所有快取，不必逐筆處理。建立 Pull Request（PR，把程式修改送人審核的請求）時，如果 head 與 base ref 相同，gh pr create 也會直接報錯；同一個起點與目標沒有可合併的差異，早點停下比建立後才發現更省事。貢獻指南同時改得更清楚，並記錄了兩位首次貢獻者。像整理倉庫時按區清空舊紙箱，門口也先攔住要把同一份文件送給自己的表單。

You can now get to Copilot CLI from the same terminal workflow you use for GitHub. Run gh copilot and gh will offer to install Copilot CLI if it is missing, then launch it. Add arguments or flags after the command and gh passes them through to Copilot CLI unchanged. Copilot has not gained a new capability here; the update simply joins installation and launch into one route instead of making you find a separate installer and switch commands, like buying a ticket and boarding at the same station counter.

You can now clear all cached results attached to one ref—a Git name that points to a branch or version—with a single gh cache delete action instead of removing them one by one. gh pr create also now errors when its head and base refs are identical, because there is nothing to merge between the same starting point and destination. The contributor guide was clarified, and the release records two first-time contributors. It is like emptying every old box in one warehouse aisle while a guard stops a form addressed from you to you before it reaches the desk.