.gitbay/wiki/Parity.org

A capability lands over SSH first. If it belongs to the triage/review/respond loop, it lands on the web in the same merge request. Anything whose input is a credential — secrets, mirror tokens, API tokens — stays SSH-only by design: the web dispatcher refuses SSHOnly commands outright. Session minting is not one of them: what a browser submits to ask for a login link is a username or an address, and the credential it gets back travels by mail.

Rows are one page or one action each. Grouped rows hide gaps, twice now: "browse, log, blame, search" read as covered while blame had no command at all, and "build list, log" read as covered while the job list a trigger can name had none (krz/gitbay#50), leaving the picker browser-only and the iOS build screen unable to say more than the log.

Reviews and checks carry the time they last said something, and a ci/<job> check carries how long its build ran, so a merge request reads without opening the build. Statuses posted through status set have no build and report only the time. A merged or closed merge request names who resolved it and when; a row without that stamp — a migrate import, or one merged before krz/gitbay!137 with no mr.merged event to backfill from — says neither rather than inventing a time.

A merge request whose target is another open merge request's source branch is stacked on it: mr show and the page say so both ways, and when the lower one merges, everything stacked on it is retargeted onto what it merged into with its reviews kept. A squash or rebase merge is refused while anything is stacked on the merge request, since it would rewrite the commits the stack builds on. All three surfaces show the stack both ways.

A draft merge request is open but not asking: it does not merge, and it does not appear in anyone's review queue. Draft is a flag rather than a fifth state, so every state = 'open' rule still means what it did. mr revisions lists the heads a merge request has had; the web page lists them beside the reviews they staled, and the iOS client has a Revisions section. mr range-diff compares two heads: the iOS client shows it from a revision to the one before, as text; the web has no view. Batched review is not built.

mr review request --add <user> asks a particular person, who then carries the merge request in their queue and is notified; --remove withdraws the ask. Without one the queue is computed from involvement — what you own, are granted, or reach through an org or team — so a collaborator with write access who has not touched a thread hears nothing until they do (krz/gitbay#145).

Creating from a fork works anywhere the source can be typed as owner/name:branch. The web's source picker offers the branches of every fork the viewer can push to in that form, and the repository header has the fork control, so the whole path — fork, edit a file, propose — runs in a browser. Retargeting moves an open merge request onto another branch of the same repository and stales the reviews, since an approval was of the diff against the old branch.

Labels are created on the fly by issue label --add and managed by label list, label set <label> --color rrggbb and label remove, which takes the label off every issue. The web paints the stored colour on every chip and derives one from the name when none is set. The set itself is at /<owner>/<repo>/labels, linked from the issue list: create, recolour and remove, dispatching the same commands.

Issue, MR and release bodies, and their comments, carry the markup they were written in — --format md|org on create, comment and edit, stored alongside the text so changing a preference later cannot reinterpret prose that already exists. Every surface renders the stored format, and every surface now offers the choice: the web's create forms, and the iOS composer on create, edit and comment. An edit starts on the format its body was stored in, since starting elsewhere would silently reinterpret it on the next save. Diff-line comments have no format column and are always markdown.

No row is web-only any more. Blame, file editing, log at a ref, archive, the public listing and the wiki were all in that state — a handler reading git or the store directly instead of dispatching a command — until krz/gitbay!99, !101 and !102 gave them commands.

build cancel withdraws a queued build, or ends a running one: the server closes the runner's log session and the runner kills the step within a couple of seconds. Cancelling a duplicate of a commit that already passed the job puts that result back on the commit. The build page carries the button while a build is still cancellable.

A pin and a bookmark are different things and are stored separately. A pin is private quick access to what you are working on, and drives the rail; a bookmark is public, says a repository is worth coming back to, and its count is the only popularity signal on the instance. Bookmarking needs read access only — it is something you do to someone else's repository — and a repository bookmarked while public and since made private drops out of the listing rather than leaking that it exists (krz/gitbay#146).

The web's watch and pin controls write the store directly instead of dispatching repo watch and repo pin. That is why the web cannot mute: its toggle knows watching and default only.

Dependency checks are off until a repository's admin turns them on: the check tells a public registry what the repository depends on. repo deps status lists what is behind; the repository's settings page renders the same report under the toggle — last check, last error, the tracking issue, and the rows. The issue the worker opens, rewrites and closes is still the copy every other surface reads.

The wiki row covers reading. A wiki lives at .gitbay/wiki/ on the default branch, so editing one is editing a file in the repository — a push, or repo commit-file — and there is no wiki-specific edit row to have parity on. The web editor reaches it on any repository that permits server-authored commits; one requiring verified signatures does not, because the server signs nothing on a user's behalf, so those wikis are push-only.

n/a marks a capability deliberately absent from a surface rather than missing from it. Archive download is n/a on iOS: the read API carries a command's stdout as a JSON string, so a gzip stream cannot survive it, and the app has nowhere useful to put a tarball — the brief rules out local git, so there is no clone, checkout or build to feed. The web's route stays the way to get one. release asset add is n/a on iOS for the same reason from the other direction: the file arrives on stdin, which the API carries as a JSON string. Attaching a runner is n/a on iOS for a plainer reason: the key is generated by gitbay-runner init on the machine that will run builds, and that machine's terminal (the command init prints) or the settings page is where the paste happens. A phone has neither the key nor the runner.

A README or wiki page's org renders per surface: the web through go-org, the iOS client through the shared OrgSwift package (krz/org-swift). OrgSwift is held to orgo's output by the krz/org-conformance corpus — golden renderings from orgo, itself diffed against Emacs ox-html — so constructs the iOS client used to approximate (tables, footnotes, timestamps, heading tags, nested lists) now render the way the reference does. go-org is not yet on the corpus.

explore is the listing without a query; repo search is the one with. search is both plus the title and body of every issue and merge request the caller can read, over FTS5; the web serves it at /search with a field in the rail, and an anonymous visitor gets the public rows from the same query. issue list --search and mr list --search narrow one repository. What someone types is quoted term by term, so an FTS5 operator — c++, AND, a lone quote — is a word to match and never a syntax error. repo grep remains the per-repository file-contents search.

About text renders as markdown or org-mode per the about_format it was stored with. The iOS client decodes and renders both, through the same OrgSwift path a README takes.

help lists the command registry. Bare it is an index, one line per command, sorted. With a prefix (help mr) it adds each command's argument syntax, which is the only place flags are written down; gitbay <cmd> --help asks the server for the same thing, and --json returns {path, summary, usage}. No web page renders it, and a native client has no use for one (krz/gitbay#57).

Notifications land in an inbox row per recipient whether or not the instance sends mail, and mail is the second half when SMTP is configured. notifications list reads it, unread by default; notifications read <id>... | --all clears it; the dashboard and the web rail carry the unread count. repo watch adds you to a repository's notifications, repo mute silences it, and repo unwatch returns you to the default from either — told about work you are part of, nothing more. A mute wins over owning the repository or having written the thread.

A login link is requested from the login page by username or verified address, and arrives by mail: it works once and expires in fifteen minutes. The row is n/a for the CLI because a terminal with a registered key runs web login, which mints a link directly and needs no mail. It exists because an account with no SSH key had no way into the web at all (krz/gitbay#155). The page offers the form only when the instance has SMTP configured; there is no separate switch. The response never says whether the account exists. It is n/a on iOS for the same reason it is on the CLI, from the other end: the app authenticates with a bearer token pasted at sign-in, so a one-time link into the web unlocks nothing it can use.

The account export bundle is n/a on iOS on the archive-download argument above — a JSON bundle has nowhere useful to land on a phone, and the web route stays the way to get one.

profile set carries description, website, about and links. It is not SSHOnly — nothing about a bio is a credential, and the JSON API runs it. The account settings page has the form, and so does the iOS client: --link replaces the whole set rather than appending, so a client sends every link it keeps on every save, and --link '' is how they are cleared.

issue list, mr list, repo list, and feed take --limit <n> and --cursor <c>. Cursors are opaque; each page carries the next one. Without the flags a list stays complete, so existing scripts are unchanged. The web pages the issue and merge request lists at fifty with the same cursors; iOS pages with them too.

Build secrets, mirror configuration and tokens, custom domain claims, API token minting, web session listing and revocation, deploy keys, account and instance administration. Deleting, transferring or renaming a repository is also CLI-only, as is deleting an organization: each removes or moves what clone URLs point at, and wants a typed command, not a button.

These are the only rows where a no is intended. Everywhere else a no is work outstanding, and n/a means a surface cannot usefully carry the capability at all — see the archive note above.