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

chore: publish from main

Browse Source
This commit is contained in:
github-actions[bot]
2026-07-14 01:08:06 +00:00
parent c135c0e910
commit 9ca9e3bab8
5 changed files with 41 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/src/content/docs/learning-hub/copilot-configuration-basics.md
+22 -1
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-07-09
lastUpdated: 2026-07-13
estimatedReadingTime: '10 minutes'
tags:
- configuration
@@ -459,6 +459,17 @@ The `/settings` command (v1.0.61+) opens an interactive dialog to browse and edi
The settings dialog supports search — type to filter settings by name. Changes take effect immediately.
*(v1.0.70+)* The `/settings` command and the `/model` command both support **`--repo` and `--local` flags** for explicitly scoping which layer of settings you want to view or edit:
```
/settings --repo # view/edit repository-scoped settings
/settings --local # view/edit local (user-level) settings
/model --repo # view/edit the model pinned for this repository
/model --local # view/edit your personal model preference
```
These flags mirror the **Repo** and **Repo (local)** scope tabs available in the `/settings` dashboard (v1.0.71+), making it easier to manage per-repository vs. user-global configuration without ambiguity. In v1.0.71+, the `/settings` dashboard also shows **Repo** and **Repo (local)** tabs alongside the existing user-level view, giving you a unified place to see which settings are applied at each layer.
GitHub Copilot CLI has two commands for managing session state, with distinct behaviours:
| Command | Behaviour |
@@ -570,6 +581,16 @@ The `/pr auto` command *(v1.0.66+)* starts a self-paced automation loop that dri
`/pr auto` is ideal when you have a PR with failing tests or linting errors — let it work through failures one at a time while you focus on other things. `/pr automerge` extends this further: it continues until all CI checks pass, required reviews are approved, and the PR is successfully merged. Both commands can be monitored and stopped from `/loop` or `/every`, which register the running automation as a scheduleable loop task.
The `/delegate` command creates a **delegate PR** — a pull request that the coding agent works on autonomously. By default, the delegate PR targets your current branch. Use `--base` *(v1.0.69+)* to specify a different target base branch:
```
/delegate # create a delegate PR targeting the current branch
/delegate --base main # create a delegate PR targeting main
/delegate --base release/2.0 # target a specific release branch
```
This is useful when you want to hand off a task to the coding agent on a specific branch — for example, backporting a fix to an older release branch or targeting a long-lived feature branch for automated work.
The `/share html` command exports the current session — including conversation history and any research reports — as a **self-contained interactive HTML file**:
```