Notify devs when sync-from-upstream infra is stuck
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
Before pushing to an existing PR, the sync infra should look at the GitHub checks and ping the devs if the situation needs intervention.
Upstream sync PRs sometimes go red: the patches won't apply cleanly, the patches or our infra causes tests to fail, or tests are flaky. There could also have a problem that makes CI hang forever (perhaps not our fault--e.g. a GitHub web hook outage). For any of these reasons, a dev should probably get involved.
Related, more issues that need extra sync logic to fix:
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the upstream-sync code and its GitHub checks and PR-update path; done means developers are notified when sync checks fail, remain flaky, or hang and require intervention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100