How we run this repo. Not for reporters — this is for the team.
Someone does a pass over needs-triage each working day:
- Duplicate? Close it, label
duplicate, link the original. - Support question in the wrong place? Point them to Support, close it.
- Missing detail? Ask, label
needs-info. Auto-close stale ones after a couple of weeks of silence. - Real bug or good request? Reproduce or accept it, then label
confirmed. Removeneeds-triage. - From a Champion? Add the
championlabel so we can filter their reports.
The repo is connected to Linear with GitHub Issues Sync, pointed at the Support team.
- We gate on the
confirmedlabel so the Support board only fills with triaged issues — not every raw report. (Set this in the sync config; confirm the exact behaviour when wiring it.) - The sync is two-way: status changes and comments in Linear flow back to the GitHub thread, which is how the reporter stays informed.
- If someone pastes a token, key, or personal data, edit it out of the issue (or hide the comment) straight away.
- Security reports filed here by mistake: don't discuss the detail in public. Close, tell them to email security@streamelements.com, and delete the sensitive parts.