Skip to content

Add instructions for Copilot Code Review #1607

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
merged 1 commit into from
Oct 28, 2025
Merged

Add instructions for Copilot Code Review #1607

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
6 changes: 6 additions & 0 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# For Copilot Code Review
- Every image change must bump the version in the image's `manifest.json` using semantic versioning.
- Breaking changes (for example, swapping the base OS) require a major bump; new non-breaking features require a minor bump; security or bug fixes require a patch bump.
- Adding a variant means updating the architecture entry in `manifest.json`, listing the variant in `variantTags`, and setting it as `latest` unless it is a preview.
- Keep the README in sync: update variant tables, tags, and version references to match the manifest.
- Example: PR #1548 switched `src/typescript-node/.devcontainer/Dockerfile` to the `4-*` JavaScript base, so `src/typescript-node/manifest.json` moved from 3.0.3 to 4.0.0, added the `*-trixie` variants to both `variants` and `build.architectures`, updated `variantTags`, and set `build.latest` to `24-trixie`; `src/typescript-node/README.md` then reflected the new default tags.