GitHub
live · conformance passing
Models an account and its organization, their repositories and default branches, issue and pull-request numbering, review and merge state, labels, comments, Projects v2 boards over GraphQL, and both rate-limit windows.
- Category
- Developer tools
- Sandbox key
- github_pat_…
- Verified against
- octokit 5.0.5
- Replaces
- A throwaway organization, a real token in CI, recorded fixtures
Scenarios
Start a sandbox in one of these, or describe the state you want in a sentence and the seeder writes the records it implies.
Busy repository
A repository with open and closed issues and a discussion.
Archived repository
A repository that has been archived, so every write is refused.
Issues disabled
A repository with its issue tracker turned off.
Locked issue
An issue locked to collaborators, so its reason is set.
Pull request in review
An open pull request on a branch, already mergeable, discussed.
Merge conflict
A pull request whose head conflicts, so merging is refused.
Organization workspace
The organization with two repositories and the operator an owner.
Project board
A Projects v2 board with a status field and three issues on it.
Rate-limited token
The hour's REST rate limit is spent, so every call is refused.
What it models
Records your code can read, write and edit for the life of the sandbox. A route the twin does not model returns a provider-shaped refusal rather than a plausible response.
- users
- tokens
- organizations
- repositories
- branches
- issues
- pull_requests
- comments
- labels
- projects
- project_items
Verified in CI against
- nodeoctokit5.0.5