Skip to content

docs(contributing): say when an enhancement is retired #8

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

docs(contributing): say when an enhancement is retired #8

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: 4 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,10 @@ Ordinary git and GitHub practice — opening an issue, naming a branch, writing

See [`docs/security.md`](docs/security.md) for the extension's security model and a reviewer checklist.

## When an enhancement is retired

An enhancement is a proposal, so it has an end. **Retire it once the product ships an equivalent** — delete its file and its registry entry in a small PR — or when the proposal is declined and it no longer earns its place in demos. Discussion with the product team about a proposal happens, and is tracked, **outside this repo**; nothing here links to it, and an enhancement's text does not record how it was received (see *Public repository* above).

## Workflow

Issue → worktree → PR → squash-merge → **reload the extension from the primary checkout**.
Expand Down
Loading