unify the two github clients used in this repo
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 363
- Forks
- 369
- Avg merge
- 1d 54m
- Merged PRs (30d)
- 59
Description
This repo uses two different GitHub client abstractions:
- https://github.com/rust-lang/team/blob/3dabff8830a7599ff0b1ae35a219ff06bf6285b7/src/api/github.rs#L39
- https://github.com/rust-lang/team/blob/3dabff8830a7599ff0b1ae35a219ff06bf6285b7/src/sync/github/api/mod.rs#L45
We should unify them
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 comparing src/api/github.rs and src/sync/github/api/mod.rs, the two abstractions named in the issue. Trace their callers to understand which interfaces are required and where they overlap. Done means the repository uses one unified GitHub client abstraction without the duplicated implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100