Repository navigation
docs: require Playground reproductions for issues - #1286
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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e7bcbdb308
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 3. Select a concrete **Version** instead of `latest` so the reproduction stays | ||
| tied to the engine version you tested. |
There was a problem hiding this comment.
A concrete ?version= does not keep a reproduction tied to that engine indefinitely: scripts/stage-playground-wasm.mjs publishes only the newest ten releases and removes older WASM files, while initialLintVersion silently selects latest when the requested version is no longer in the manifest. After ten subsequent releases, an old issue link will therefore run a different engine while retaining its stale version parameter, potentially hiding or changing the reported bug. Retain pinned releases or make unavailable versions fail explicitly rather than promising durable version-specific reproductions.
Useful? React with 👍 / 👎.
1 participant
Summary
Require a Playground reproduction URL when opening a utoo-lint issue. Add an issue form with required reproduction, steps, expected behavior, and actual behavior fields, and disable blank issues.
Document how to create and verify a minimal Share URL with a concrete engine version, provide additional CLI/filesystem reproduction details, and verify a released fix before closing the issue. Link the process from the README. The form requires a non-empty URL field; link validity is checked during triage.
Test Plan
git diff --cached --checkpassed before committing.