You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(interrupt-rotation): clarify required work vs reference views (#75)
Make it visually clear which dashboard sections the person on Interrupt must
handle. Group the mandatory sections under an "Action required" header and move
the informational sections under a collapsed "For reference" zone.
Since new community PRs are no longer accepted, demote the Community PRs section
to a read-only, informational view with a banner stating no action is required.
Disambiguate the "Confirmed bugs without a reproducible script" help text: a
"reproducible script" means a runnable repro committed to st-issues or the agent
wiki, not the "Reproducible Code Example" snippet that most issues carry from the
bug-report template. This resolves recurring confusion about why issues with a
code snippet still appear in the list.
Also apply Streamlit design guidance: drop heavy dividers, use Material Symbols
icons over emojis, sentence casing, and lighter captions for empty states.
Confirmed bugs (`status:confirmed` & `type:bug`) created in the selected timeframe that don't have a reproducible script.
495
490
496
-
This isn't a requirement for all issues. If the issue is not easily reproducible via the [streamlit/st-issues](https://github.com/streamlit/st-issues) app, you can skip this step.
491
+
**"Reproducible script" here means a runnable repro committed by the team**, either a `gh-<issue-id>` folder in [streamlit/st-issues](https://github.com/streamlit/st-issues) or an `issues/<issue-id>/repro_app.py` in the agent wiki. It does **not** mean the "Reproducible Code Example" snippet in the issue body - most issues have that from the bug-report template, so it doesn't count here.
492
+
493
+
**Reviewing this list is required during your rotation.** Adding a reproducible script itself is best-effort: if a bug isn't easily reproducible via the [streamlit/st-issues](https://github.com/streamlit/st-issues) app, it's fine to skip writing a script, but you should still confirm the bug is triaged and prioritized correctly.
497
494
498
495
**How to add a new repro case to [streamlit/st-issues](https://github.com/streamlit/st-issues):**
499
496
1. [Create a new folder in `issues`](https://github.com/streamlit/st-issues/new/main/issues) with this naming pattern: `gh-<GITHUB_ISSUE_ID>`.
0 commit comments