GitHub CLI 2.87.0

下載 gh 的新版本時，授權資訊現在會在發布階段一併打包。授權條款是說明程式碼能如何使用與散布的規則；把它們跟著成品整理好，使用者或公司在檢查這套工具包含哪些授權時，不必再另外拼湊資料。這不會改變你下指令的方式，而是讓每一份發布品的文件更完整，也方便保存與交接。就像買電器時，保固與使用說明直接放進盒子，不必回頭向不同廠商索取。

整理 GitHub 專案看板時，gh project item-list 現在可加上 --query 旗標（指令後用來指定做法的選項），用查詢條件挑出想看的項目，不必先把整張清單都撈出來再自己找。這特別適合待辦很多、只想聚焦某類項目的看板。隨後也整理了這項查詢功能加入時的程式碼，讓它維持一致。就像圖書館目錄多了一個搜尋欄，你先寫好條件，再拿到需要的那排書。

你手動啟動 GitHub Actions 工作流程（workflow，依步驟自動執行工作的設定）後，gh 現在能取得這次手動觸發執行的詳細資料。以前看執行紀錄時，手動按下啟動的那一趟可能少了可追查的資訊；現在工具會把它當成可辨識的一次執行來讀取。這讓你檢查部署、測試或其他自動化工作時，更容易確認剛剛啟動的是哪一次。就像叫了外送後能看到那一張訂單，而不是只知道店家曾經出餐。

用 gh 與 GitHub 溝通時，REST API（讓程式透過網址交換資料的介面）現在固定使用 2022-11-28 這個版本。API 若隨服務端預設版本變動，原本可用的指令回應可能在沒有改動你的情況下改變；明確指定版本，工具就知道要依哪一套規則交談。這不是讓你多背一個日期，而是替日常指令減少不預期的差異。就像填表時固定拿同一版表格，不會今天欄位忽然換了位置。

檢查工作流程執行結果時，就算你同時要求顯示完整日誌或只顯示失敗日誌，gh run view 的 --exit-status 旗標（讓指令以成功或失敗結果結束的選項）現在也會照實回傳結果。以前加上 --log 或 --log-failed 後，這個判斷可能沒有被遵守，讓腳本看錯執行是否失敗。現在你既能讀日誌，也能讓自動化據此停下或繼續。就像警報紀錄可查看，警示燈也仍會亮起。

用 gh pr create 建立提取請求（PR，把你的修改送去請專案合併的申請）而需要分叉（fork，複製別人的專案到自己的帳號）時，gh 現在只會分叉預設分支，不再一口氣複製所有分支。你要送出的改動通常是從預設分支開始，這樣做能把建立 PR 時搬運的範圍縮小到真正需要的部分。原專案的其他分支不會因此被當成這次建立 PR 必須帶走的內容。就像只影印辦事所需的主文件，不把整個檔案櫃都搬回家。

編輯提取請求（PR，把修改送去請專案合併的申請）時，你現在能在互動式提示裡挑選指派人，並可搜尋後把 Copilot 加為審查者。互動式提示是指令一步步問你要選什麼的畫面，因此不必自己記住每個帳號再手打。這兩處也改善了操作速度與無障礙功能，讓使用輔助工具的人更容易完成選擇。就像填會議邀請時，可在名單中找人、勾選 AI 助手，欄位也更好操作。

上傳發布檔時，gh release upload 對 --clobber 旗標的說明更明白：它會先刪除既有資產，再重新上傳，而不是直接覆蓋得像沒發生過事。gh gist edit 也加入使用範例，方便你編輯 gist（用來分享短程式碼或文字片段的 GitHub 貼文）。另外修正一處英文拼字。這些改動不改指令功能，卻把可能誤操作的地方先講清楚。就像搬新檔前先在按鈕旁寫明「會先清空舊櫃」。

這一批也整理了 gh 的內部維護：移除回饋 issue 範本、把 issue 與 PR 分流流程搬到共用工作流程、補上功能偵測註解，並讓升級 Go 的工作流程可手動啟動；程式碼錯誤格式與文件來源也做了修正。底層同時更新 Go、OAuth、文字、終端機、簽章與發布相關依賴套件，另記錄一位新貢獻者。這些不是新增給你下的新指令，而是維持開發、測試與發布鏈條。就像店面不添新菜，先把廚房管線和備料流程整理好。

When you download a new gh release, its license information is now bundled during the release process. Licenses state how code may be used and distributed, so having them collected with the finished download makes it easier for a person or company to review what is included. This does not change any command you run; it simply makes each release package more complete. It is like getting the warranty and manual in the appliance box instead of requesting them from several manufacturers.

When organizing a GitHub project board, gh project item-list can now take a --query flag, an option that tells a command how to act. You can use a query to select the items you need instead of retrieving the entire list and searching through it yourself. That helps on boards with many tasks when you only want one kind of item. The accompanying implementation was also cleaned up. It is like adding a search box to a library catalog before you walk to the shelf.

After you manually start a GitHub Actions workflow, gh can now retrieve details for that dispatched run. A workflow is a configured sequence of automated steps. Previously, a run started with the manual button could have less traceable information when you reviewed executions. Now the tool recognizes and retrieves it as a specific run, making it easier to check which deployment, test, or automation job you just started. It is like being able to see your own delivery order instead of only knowing the restaurant sent food at some point.

When gh communicates with GitHub, it now pins the REST API to version 2022-11-28. A REST API is an interface through which programs exchange data over web addresses. If the service's default API version changes, a command response can change even though you changed nothing. Naming one version tells gh which set of rules to use. You do not need to memorize the date; it simply reduces surprise differences in everyday commands, like always receiving the same version of a form.

When checking a workflow run, gh run view now honors its --exit-status flag even when you ask for full logs or failed logs. The flag makes a command end with a success or failure result. Previously, combining it with --log or --log-failed could lose that signal, causing a script to misread whether the run failed. Now you can inspect the logs while automation still knows whether to stop or continue. It is like being able to read an alarm record while the warning light still stays on.

When gh pr create needs to fork a repository while creating a pull request, it now forks only the default branch instead of every branch. A pull request is a request to merge your changes into a project, and a fork is your own copy of someone else's repository. Since your change usually begins from the default branch, this narrows what must be copied for the task. Other branches are not treated as required baggage. It is like photocopying the main document you need rather than carrying home the whole filing cabinet.

When editing a pull request, you can now choose an assignee in an interactive prompt and search for Copilot to add it as a reviewer. A pull request asks a project to merge your changes, while an interactive prompt asks you for choices step by step, so you do not have to remember and type every account name. Both areas also received performance and accessibility improvements, making the selection easier with assistive tools. It is like filling out a meeting invitation with a searchable attendee list and an AI assistant checkbox.

When uploading a release asset, gh release upload now explains --clobber more clearly: it deletes an existing asset before uploading again. gh gist edit also gains usage examples, making it easier to edit a gist, GitHub's short post for sharing code or text snippets. One English typo was corrected as well. These changes do not alter the commands' core behavior, but they make a potentially destructive action easier to understand before you use it. It is like labeling a button to say it empties the old cabinet first.

This release also tidies gh's internal maintenance: it removes a feedback issue template, moves issue and PR triage to shared workflows, adds feature-detection notes, and lets the Go bump workflow be started manually. Error formatting and source-document checks were fixed, while Go, OAuth, text, terminal, signing, and release-related dependencies were updated; a new contributor was also recorded. These are not new commands for you to type. They maintain the development, testing, and release chain, like improving kitchen plumbing and prep work without adding a new dish to the menu.