-
Notifications
You must be signed in to change notification settings - Fork 2
[task] Add GitHub API adapter using gh api #4
Copy link
Copy link
Open
Labels
area: coreShared Rust product logic and domain behavior.Shared Rust product logic and domain behavior.kind: maintenanceRepository maintenance or infrastructure work.Repository maintenance or infrastructure work.maintainer onlyRepository administration or governance work reserved for maintainers.Repository administration or governance work reserved for maintainers.
Milestone
Metadata
Metadata
Assignees
Labels
area: coreShared Rust product logic and domain behavior.Shared Rust product logic and domain behavior.kind: maintenanceRepository maintenance or infrastructure work.Repository maintenance or infrastructure work.maintainer onlyRepository administration or governance work reserved for maintainers.Repository administration or governance work reserved for maintainers.
Goal
Add the first Rust adapter for reading GitHub data through
gh api.Why this matters
Nexgit's MVP is GitHub-first, but it should not make contributors solve token storage or OAuth before the app-server data shape is proven.
gh apilets Nexgit reuse existinggh authwhile keeping GitHub calls inside Rust-owned code.Command/API target
Create a small adapter that can run REST and GraphQL
gh apicalls with explicit arguments and return stdout, stderr, and exit status in a testable shape.Depends on
None. This is the foundation for the GitHub App-Server Data milestone.
Out of scope
octocrabor another GitHub client yet.Definition of done
gh apicalls can be represented without panics.ghdirectly.Verification
cargo fmt --all --checkcargo check --workspaceContributor notes
This is maintainer-owned because it sets the implementation pattern for later contributor issues.