[OSS CI] Set up viable/strict SLA alert
Open
@psiddh is already working on this.
Since May 30, 2026.
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
Objective
Set up automated alerting when viable/strict has not advanced
SLA Definition
3 days without viable/strict movement → Raise an alert and keep alerting or flagging
Action Items
- Determine how to monitor viable/strict advancement (HUD API? periodic check?)
- Set up alerting mechanism
References
HUD: https://hud.pytorch.org/hud/pytorch/executorch/main
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.