oxidecomputer / oxidecomputer/rfd-api
Improve filtering during scan
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 95
- Forks
- 22
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 17
Description
While scanning for RFDs we currently add a job for each published RFD. We could be smarter about this but analyzing the files in each published RFDs directory to see if we have already processed the latest commit in that directory.
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
Start by locating the scanner and the code that creates a job for each published RFD, then inspect how files in published RFD directories expose their latest commit. Confirm how processed commits are recorded before changing the filtering. Done means scanning skips directories whose latest commit was already processed while still creating jobs for newer commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100