oxidecomputer / oxidecomputer/buildomat
handle installation_repositories events and update the repository cache
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
We receive webhook deliveries with the event field set to installation_repositories, and the payload.action field set to either added or removed. We should at least use the removed events to ditch old cached values. Otherwise, things can become confused when a repository is deleted and then another repository is subsequently created with the same name later.
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
Search the Rust source for webhook event dispatch and the repository cache, then trace how installation repository events are handled. Confirm that removed events invalidate cached repository values and that added events remain compatible; add or update tests if the existing webhook test area is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100