Skip to content

docs: enhance clarity in course updater workflow by specifying comparison with existing PRs #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DanWahlin merged 1 commit into from
Apr 6, 2026
+2 −2
Merged

docs: enhance clarity in course updater workflow by specifying comparison with existing PRs #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions .github/workflows/course-updater.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,11 +37,11 @@ Look for:
- Significant changes to existing features (renames, deprecations)
- New customization options (e.g. instructions, agents, skills, MCP, plugins)

## Step 2 — Compare against the current course content
## Step 2 — Compare against the current course content and existing PRs

This course targets beginners so only include content changes that would cater to that audience. For example, if a new feature is advanced or doesn't qualify as a "beginner" level feature, it may not be necessary to include it in the course content since we don't want to overwhelm learners. Determine what is most relevant and helpful for beginners learning about the Copilot CLI.

Read the readme files in the repo and compare the features documented there against what you found in Step 1.
Read all of the readme files in the repo and compare the features documented there against what you found in Step 1. Also check existing pull requests to see if any updates are already in progress. DO NOT duplicate efforts if an update has already been proposed in an open PR.
Copy link

Copilot AI Apr 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use the conventional capitalization “README” (and “README files”) instead of “readme” for clarity and consistency with typical filename casing in repos.

Suggested change
Read all of the readme files in the repo and compare the features documented there against what you found in Step 1. Also check existing pull requests to see if any updates are already in progress. DO NOT duplicate efforts if an update has already been proposed in an open PR.
Read all of the README files in the repo and compare the features documented there against what you found in Step 1. Also check existing pull requests to see if any updates are already in progress. DO NOT duplicate efforts if an update has already been proposed in an open PR.

Copilot uses AI. Check for mistakes.
Identify:

- **Missing features** — new capabilities not yet documented
Expand Down
Loading