Clarify startup message "No copilot-instructions.md found" to specify it means the repo-scoped file

未關閉 適合新手
#4,475 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
1/5
預估耗時
1-3 小時
新手友好度
72/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
冷清
技術堆疊
shell
領域
cli

研究方向

從發出 "No copilot-instructions.md found." 的 CLI 工作階段啟動路徑開始,追蹤如何檢查儲存庫範圍的指示。更新措辭,以指出缺少的儲存庫範圍檔案,同時保留使用者範圍和其他指示來源的行為;在啟動期間以及使用 /env 或 /instructions 時驗證結果。

由索引模型根據 Issue 內容生成。

描述

area:context-memory
Describe the feature or problem you'd like to solve

On session start, the CLI prints "No copilot-instructions.md found." This wording is ambiguous.

Proposed solution

On session start, the CLI prints "No copilot-instructions.md found." This wording is ambiguous — it reads as though NO custom instructions were loaded at all, when in fact it only means the repository-scoped file (.github/copilot-instructions.md in the git root/cwd) is absent.

A user-scope file at $HOME/.copilot/copilot-instructions.md (and other supported sources like AGENTS.md, CLAUDE.md, $HOME/.copilot/instructions/**) may still be fully loaded and active. The current message caused me to believe none of my instructions were in effect, when my user-scope instructions actually were loaded.

Requested change / proposed solution: reword the message to name the specific missing file/scope, e.g. "No repository-scoped .github/copilot-instructions.md found" — and ideally note that user-scope or other instruction sources may still be active.

Benefits to GitHub Copilot CLI and its users:

  • Removes a misleading signal that makes users think their instructions aren't loaded.
  • Reduces confusion and wasted time spent debugging a non-issue.
  • Sets accurate expectations about which instruction scope is missing vs. active.
  • Encourages correct use of layered instruction sources (repo-scoped vs. user-scoped).
Example prompts or workflows
  1. User has a populated $HOME/.copilot/copilot-instructions.md with personal workflows.
  2. User starts a session in a repo that has no .github/copilot-instructions.md.
  3. CLI prints "No copilot-instructions.md found."
  4. User reasonably concludes NONE of their instructions loaded — but the user-scope file is active.
  5. Running /env confirms the user-scope instructions ARE loaded, contradicting the startup message.

Suggested improved message:
"No repository-scoped .github/copilot-instructions.md found. (User-scope and other instruction sources, if present, are still active — see /env or /instructions.)"

Additional context
Image
主要語言
Shell
星號
11.2k
分支
1.9k
平均合併
14 小時 16 分鐘
30 天內合併 PR
6

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/copilot-cli 的其他 Issue

查看 github/copilot-cli 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。