chore: publish from staged

This commit is contained in:
github-actions[bot]
2026-06-24 00:31:28 +00:00
parent 188571197c
commit 2716f6f5e5
5 changed files with 44 additions and 11 deletions
@@ -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-05-13
lastUpdated: 2026-06-23
estimatedReadingTime: '10 minutes'
tags:
- configuration
@@ -410,6 +410,8 @@ The model picker opens in a **full-screen view** with inline reasoning effort ad
**Auto mode and server-side model routing** (v1.0.43+): When you select **Auto** as your model, the CLI uses server-side model routing for real-time model selection. Instead of locking in a single model at session start, Auto mode evaluates each request and routes it to the most appropriate model dynamically. This means straightforward questions can be handled by a faster model while complex reasoning tasks are automatically escalated — without you needing to switch models manually.
**Model family aliases** (v1.0.64+): Instead of typing a full model name, you can use short family aliases in the model setting: `opus`, `sonnet`, `haiku` (Anthropic), and `gpt`, `gemini` (Google/OpenAI). The CLI resolves the alias to the latest available model in that family. This is especially useful in scripts or configuration files where you want to track the best model in a family without hardcoding a version string.
### CLI Session Commands
GitHub Copilot CLI has two commands for managing session state, with distinct behaviours:
@@ -465,11 +467,12 @@ The `/undo` command reverts the last turn—including any file changes the agent
Use `/undo` when the agent's last response went in an unwanted direction and you want to try a different approach from that point.
The `/fork` command (v1.0.45+) copies the current session into a **new independent session** that starts from the same conversation state. The original session continues unchanged — you can switch back to it at any time. This is useful when you want to explore two different approaches to a problem simultaneously:
The `/fork` command (v1.0.45+) copies the current session into a **new independent session** that starts from the same conversation state. The original session continues unchanged — you can switch back to it at any time. This is useful when you want to explore two different approaches to a problem simultaneously. In v1.0.64+, `/branch` is available as an alias for `/fork` (matching Claude Code's command naming):
```
/fork # fork with an auto-generated name
/fork "my-experiment" # fork with a custom name (v1.0.47+)
/branch # alias for /fork (v1.0.64+)
```
After forking, the new session is immediately active. Both sessions share the same history up to the fork point but accumulate changes independently from that moment forward. Use `/fork` to experiment with a risky refactor without abandoning your current working session. Since v1.0.47, forked sessions display their **origin session** name in the sessions dialog, making it easy to trace which session a fork came from.