github-samples / github-samples/pets-workshop
full-day workshop: Refresh Copilot terminology and model-specific guidance
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 80
- Forks
- 161
- Avg merge
- 31m
- Merged PRs (30d)
- 1
Description
Problem
The full-day content hard-codes Copilot details that change independently of the workshop:
5-context.mdfocuses on the@workspaceparticipant and a free-trial signup flow.6-code.mdsays repository custom instructions are available only to Chat.6-code.mdrequires Edit mode and recommends the account-dependentClaude 3.7 Sonnetmodel.- The devcontainer installs both
GitHub.copilotandGitHub.copilot-chat, which should be checked against the current extension packaging.
These instructions can diverge from the stable VS Code experience based on extension version, account plan, organization policy, and model retirement.
Suggested change
Validate Exercises 3, 5, and 6 against the current stable Copilot experience. Prefer capability-based language and treat named models as optional examples.
Acceptance criteria
- Current mode, context, custom-instruction, and extension terminology is used consistently.
- Statements about where custom instructions apply are accurate.
- Model selection does not require a specific optional or retired model.
- Signup language reflects current Copilot access options.
- Screenshots and controls match a current stable VS Code installation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review Exercises 3, 5, and 6, especially 5-context.md, 6-code.md, and the devcontainer configuration. Compare their Copilot terminology, access guidance, model references, extensions, controls, and screenshots with a current stable VS Code installation. Done means the acceptance criteria are met without requiring a specific model or outdated access flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, vscode
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100