Start tracking drift between main and viable/strict
Open
Nobody has claimed this yet.
module: build/install
module: ci
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
To improve the reliability of CI, let's start measuring the drift between main and viable/strict. Once we have this, we should configure oncall alerts when it exceeds x days.
If you have context of how we can do this, please leave a comment. Specifically how we can get this into intern to configure oncall alerts.
cc @larryliu0820 @lucylq @mergennachin @byjlw
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.
Research direction
No files, tests, or entry points are named. Start by locating the CI configuration that builds or compares main and viable/strict, then investigate how intern can configure oncall alerts; done means drift is measured and an alert threshold is defined and connected to oncall.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- ci-cd, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100