Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-04-12 03:05:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update Learning Hub for CLI v1.0.10/v1.0.11 features (#1150)

Browse Source 
- Add monorepo support section to copilot-configuration-basics:
  customizations discovered at every directory level up to git root
- Add personal skills directory (~/.agents/skills/) documentation
- Add /clear vs /new session command distinction + /undo command
- Add MCP organization policy enforcement to understanding-mcp-servers
- Add sessionStart additionalContext injection to automating-with-hooks
- Add extension hooks merging behaviour to automating-with-hooks

Source: https://github.com/github/copilot-cli/releases/tag/v1.0.11
Source: https://github.com/github/copilot-cli/releases/tag/v1.0.10

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
github-actions[bot]
2026-03-25 09:59:45 +11:00
committed by GitHub
parent 7471eb5492
commit f1004d04c0
3 changed files with 88 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
website/src/content/docs/learning-hub/copilot-configuration-basics.md
View File

@@ -3,7 +3,7 @@ title: 'Copilot Configuration Basics'
description: 'Learn how to configure GitHub Copilot at user, workspace, and repository levels to optimize your AI-assisted development experience.'
authors:
- GitHub Copilot Learning Hub Team
lastUpdated: 2026-03-23
lastUpdated: 2026-03-24
estimatedReadingTime: '10 minutes'
tags:
- configuration
@@ -170,6 +170,43 @@ A well-organized Copilot configuration directory looks like this:
└── api-design.instructions.md
```
### Monorepo Support
In monorepos with multiple packages or services, GitHub Copilot CLI discovers customizations at **every directory level** from your working directory up to the git repository root. This means each package or service can have its own `.github/` folder with specialized agents, instructions, skills, and MCP servers, while still inheriting configuration from parent directories.
```
my-monorepo/
├── .github/
│ └── instructions/
│ └── shared-conventions.instructions.md ← applies everywhere
├── packages/
│ ├── api/
│ │ └── .github/
│ │ └── agents/
│ │ └── api-expert.agent.md ← applies in packages/api/
│ └── web/
│ └── .github/
│ └── instructions/
│ └── react-conventions.instructions.md ← applies in packages/web/
```
When you work inside `packages/api/`, Copilot loads configuration from `packages/api/.github/`, then `packages/.github/` (if it exists), then the root `.github/`. This layered discovery ensures the right context is active no matter where in the repository you're working.
### Personal Skills Directory
In addition to repository-level skills, GitHub Copilot CLI supports a **personal skills directory** at `~/.agents/skills/`. Skills you place here are discovered automatically across all your projects, making them ideal for personal workflows and reusable utilities that are not project-specific.
```
~/.agents/
└── skills/
├── my-review-style/
│ └── SKILL.md ← available in all sessions
└── cleanup-todos/
└── SKILL.md
```
This personal directory aligns with the VS Code GitHub Copilot for Azure extension's default skill discovery path, so skills defined here work consistently across tools.
### Custom Agents
Agents are specialized assistants for specific workflows. Place agent definition files in `.github/agents/`.
@@ -357,6 +394,25 @@ CLI settings use **camelCase** naming. Key settings added in recent releases:
> **Note**: Older snake_case names (e.g., `include_gitignored`, `auto_updates_channel`) are still accepted for backward compatibility, but camelCase is now the preferred format.
### CLI Session Commands
GitHub Copilot CLI has two commands for managing session state, with distinct behaviours:
| Command | Behaviour |
|---------|-----------|
| `/new [prompt]` | Starts a fresh conversation while keeping the current session backgrounded. You can switch back to backgrounded sessions. |
| `/clear [prompt]` | Abandons the current session entirely and starts a new one. Backgrounded sessions are not affected. |
Both commands accept an optional prompt argument to seed the new session with an opening message, for example `/new Add error handling to the login flow`.
The `/undo` command reverts the last turn—including any file changes the agent made—letting you course-correct without manually undoing edits:
```
/undo
```
Use `/undo` when the agent's last response went in an unwanted direction and you want to try a different approach from that point.
## Common Questions
**Q: How do I disable Copilot for specific files?**