github-samples / github-samples/pets-workshop

full-day workshop: Refresh Copilot terminology and model-specific guidance

Open
#266 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P1
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.md focuses on the @workspace participant and a free-trial signup flow.
  • 6-code.md says repository custom instructions are available only to Chat.
  • 6-code.md requires Edit mode and recommends the account-dependent Claude 3.7 Sonnet model.
  • The devcontainer installs both GitHub.copilot and GitHub.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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.