Repository navigation
chore(experiments): add registry of existing experiments - #30919
Open
ibetitsmike wants to merge 1 commit into
Open
ibetitsmike wants to merge 1 commit into
ibetitsmike wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This branch has not been deployed
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.
Adds
experiments/registry.yaml, an inventory of every experiment onmaintoday. Nothing reads it yet. It is the first piece of the experiment promotion gate: a later PR adds a lint check that keeps it in sync with the code and enforces the stage rules.The scan covered every marker the repo uses: the 17 flags in
codersdk.ExperimentsKnown, thex/directories,exp_files,/api/experimentalroutes,docs/manifeststage labels, and the frontendexperiments.includes(...)gates. Each entry records the stage, the date it entered that stage, the flag, the paths it owns, its experimental routes and its docs page. Atoolssection listsexp_files that are dev tools, not features (scale tests, debug commands).27 entries: 17 flagged experiments, 10 unflagged ones. Stage comes from the docs label. A feature behind a hidden flag with no label is early access.
Drift the scan found, recorded in each entry's
notes:x/and some routes are still under/api/experimental.mcp-server-http: the docs label the page beta, but the endpoint needs a hidden flag.notifications: nothing reads the flag since chore: remove notifications experiment #14869, but it is still a known experiment.chat-virtual-desktop: the desktop stream route and the agent desktop API are not gated by the flag./api/v2routes that do not exist.startup-coordinationandexternal-workspacesare early access by docs label only. No flag gates them.Left out: JetBrains Toolbox (labelled beta, but no gate or experimental code) and the removed
agentsandchat-automationsflags. Noownerfield yet, since there is no team mapping to fill it.Testing
A local script (not committed) checked that every path glob matches at least one tracked file, every docs page exists, the flags match
ExperimentsKnownexactly, and everyx/andexp_file belongs to an entry or a tool. Six routes are missing from swagger; each was confirmed in the router.