bevyengine / bevyengine/bevy-website
Switch from raw Github API HTTP calls to crate
- Dominant language
- JavaScript
- Stars
- 249
- Forks
- 450
- Avg merge
- 16h 20m
- Merged PRs (30d)
- 6
Description
`bevy-website`'s tools currently hand-roll HTTP calls to Github's API. This can be difficult to read and requires a lot of code. As discussed [on Discord](https://discord.com/channels/691052431525675048/692572690833473578/1273040046454341692), it may be valuable switching to an crate that handles this for us. Some options:
- [`octorust`](https://crates.io/crates/octorust), maintained by the prominent [oxidecomputer](https://github.com/oxidecomputer)
- [`octocrab`](https://lib.rs/crates/octocrab)
Contributor guide
Research direction
The issue names no files or tests. Start by locating the bevy-website tools that hand-roll HTTP calls to GitHub's API, then compare the listed octorust and octocrab crates; done means the relevant calls use a selected crate without changing their existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- api, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100