This repository's entire product premise (per README.md's opening paragraph) is external contributors doing paid work via GitHub issues-as-bounties. That makes the absence of a CONTRIBUTING.md — covering how to run make build/make test, the cargo fmt/cargo clippy -D warnings gate CI enforces, expectations for test coverage on new code, and how PRs should reference the issue(s) they close — a more consequential gap here than in a typical internal-only repo. New contributors currently have to reverse-engineer conventions from .github/workflows/ci.yml and existing PR history rather than reading a single onboarding document.
This repository's entire product premise (per README.md's opening paragraph) is external contributors doing paid work via GitHub issues-as-bounties. That makes the absence of a
CONTRIBUTING.md— covering how to runmake build/make test, thecargo fmt/cargo clippy -D warningsgate CI enforces, expectations for test coverage on new code, and how PRs should reference the issue(s) they close — a more consequential gap here than in a typical internal-only repo. New contributors currently have to reverse-engineer conventions from.github/workflows/ci.ymland existing PR history rather than reading a single onboarding document.