Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/course-updater.lock.yml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

3 changes: 3 additions & 0 deletions .github/workflows/course-updater.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ safe-outputs:
labels: [automated-update, copilot-cli-updates]
title-prefix: "[bot] "
base-branch: main
protected-files: fallback-to-issue
---

# Check for Copilot CLI Updates
Expand Down Expand Up @@ -59,6 +60,8 @@ If updates are needed, make a decision on which chapter(s) need to be updated.

If the new information can be added to existing chapter(s), edit those chapters to include refinements, new sections, or updated information as needed. Remember that this course targets beginners, so ensure that any new content is explained clearly and simply, with examples if possible.

Only edit course content files — the chapter `README.md` files (00 - 07), the root `README.md`, `GLOSSARY.md`, `appendices/`, and files under `samples/`. Never modify repository configuration, such as anything in the `.github/` folder (including `.github/agents/` and `.github/skills/`), the `.agents/` folder, or package manifests like `package.json`. Those files are protected, and a pull request that changes them will be refused. If a new Copilot CLI feature would require changing one of those files, describe the change in the pull request body instead of editing the file.

## Step 5 — Open a pull request

Create a pull request with your changes, using the `main` branch as the base branch. The PR title should summarize what was updated (e.g., "Add /plan command documentation"). The PR body should list:
Expand Down
Loading