Conversation
…ison with existing PRs
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies the “course updater” workflow instructions so the updater also checks for in-progress work in existing pull requests before proposing new course updates.
Changes:
- Updates Step 2 heading to explicitly include comparison against existing PRs.
- Expands Step 2 instructions to check open pull requests and avoid duplicating ongoing updates.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/course-updater.md | Documentation-only clarification to include checking existing PRs during course update evaluation. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
| 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. |
There was a problem hiding this comment.
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enhances clarity in the course updater workflow by specifying comparison with existing PRs.