Expand description
Everything a person does with GitHub here, once.
A command line, a daemon serving pages, and any other surface call these and nothing beneath them. Reads come from the mirror: no token, no network, no waiting, and every answer carries how old it is. Writes go to GitHub FIRST and are mirrored from what GitHub hands back — the other order shows a change and takes it away again on the next sync, and a surface that does that is one nobody believes.
Structs§
- AllBoards
- Every board this person reaches, as the mirror holds them.
- Board
List - The boards a project references, and why any could not be shown.
- Board
Owner - One owner of boards, and how current its board list is.
- Cards
- One board’s cards and how current they are.
- Gist
Answer - A gist, and whether it came from the mirror or had to be fetched.
- Issue
List - Issues across several repositories, as the mirror holds them.
- Listed
- A list scope’s documents and how current they are.
- Repo
Facts - What the mirror knows about one repository, for a row that draws it.
- Repo
Failure - A repository whose last refresh failed, and why.
- Service
- The machine’s GitHub, read through the mirror and written through GitHub.
- Single
- A single-document scope’s document —
Nonewhen not read yet — and how current it is.
Enums§
- Failure
- Why an operation did not happen.
- Issue
State - Which issues a read wants.
- Relation
- Why an owner’s boards are listed.