.gitbay/wiki/Parity.org
284 lines · 13655 bytes
1#+title: Parity
2
3Which surface can do what. The CLI is meant to be the complete
4interface: every capability exists over SSH, and the other surfaces
5dispatch the same control commands rather than reimplementing them, so
6they cannot drift. This page is updated in the merge request that
7changes a row.
8
9Three surfaces now: the CLI over SSH, the web, and the iOS client
10(krz/gitbay-ios). A =no= in the cli column is a defect, not a
11preference — it means some surface reached around the registry and
12stranded a capability where only it can reach.
13
14* Rule
15
16A capability lands over SSH first. If it belongs to the
17triage/review/respond loop, it lands on the web in the same merge
18request. Anything whose input is a credential — secrets, mirror
19tokens, API tokens — stays SSH-only by design: the web dispatcher
20refuses =SSHOnly= commands outright. Session minting is not one of
21them: what a browser submits to ask for a login link is a username or
22an address, and the credential it gets back travels by mail.
23
24Rows are one page or one action each. Grouped rows hide gaps, twice
25now: "browse, log, blame, search" read as covered while blame had no
26command at all, and "build list, log" read as covered while the job
27list a trigger can name had none (krz/gitbay#50), leaving the picker
28browser-only and the iOS build screen unable to say more than the log.
29
30* Merge requests
31
32| capability | cli | web | ios |
33|------------------------+-----+-----+-----|
34| read, diff, commits | yes | yes | yes |
35| review and check times | yes | yes | yes |
36| who resolved it, when | yes | yes | yes |
37| comment | yes | yes | yes |
38| edit title and body | yes | yes | yes |
39| review (approve etc.) | yes | yes | yes |
40| resolve a thread | yes | yes | yes |
41| comment on a diff line | yes | yes | yes |
42| merge (all strategies) | yes | yes | yes |
43| close | yes | yes | yes |
44| create | yes | yes | yes |
45| draft, ready | yes | yes | no |
46| search title and body | yes | yes | no |
47| create from a fork | yes | no | yes |
48| retarget | yes | yes | no |
49| milestone | yes | yes | yes |
50| choose body markup | yes | no | no |
51| stacked merge requests | yes | yes | no |
52
53Reviews and checks carry the time they last said something, and a
54=ci/<job>= check carries how long its build ran, so a merge request
55reads without opening the build. Statuses posted through =status set=
56have no build and report only the time. A merged or closed merge
57request names who resolved it and when; a row without that stamp — a
58=migrate= import, or one merged before krz/gitbay!137 with no
59=mr.merged= event to backfill from — says neither rather than
60inventing a time.
61
62A merge request whose target is another open merge request's source
63branch is stacked on it: =mr show= and the page say so both ways, and
64when the lower one merges, everything stacked on it is retargeted onto
65what it merged into with its reviews kept. A squash or rebase merge is
66refused while anything is stacked on the merge request, since it would
67rewrite the commits the stack builds on. The iOS client renders the
68retarget but has no stack view yet.
69
70A draft merge request is open but not asking: it does not merge, and it
71does not appear in anyone's review queue. Draft is a flag rather than a
72fifth state, so every =state = 'open'= rule still means what it did.
73Batched review and range-diff (krz/gitbay#111) are not built.
74
75Nothing asks a *particular* person for a review. The review queue is
76computed from involvement — what you own, are granted, or reach through
77an org or team — so a collaborator with write access who has not touched
78a thread hears nothing until they do (krz/gitbay#145).
79
80Creating from a fork works anywhere the source can be typed as
81=owner/name:branch=; only the web lacks it. Retargeting moves an open
82merge request onto another branch of the same repository and stales the
83reviews, since an approval was of the diff against the old branch.
84
85* Issues
86
87| capability | cli | web | ios |
88|---------------------+-----+-----+-----|
89| read, list, filter | yes | yes | yes |
90| filter by label, assignee, author, milestone | yes | yes | no |
91| search title and body | yes | yes | no |
92| create | yes | yes | yes |
93| comment | yes | yes | yes |
94| edit title and body | yes | yes | yes |
95| close and reopen | yes | yes | yes |
96| labels, assignees | yes | yes | yes |
97| milestone | yes | yes | yes |
98| milestone list | yes | yes | yes |
99| labels: list, colour | yes | no | no |
100| choose body markup | yes | no | no |
101
102Labels are created on the fly by =issue label --add= and managed by
103=label list=, =label set <label> --color rrggbb= and =label remove=,
104which takes the label off every issue. The web paints the stored colour
105on every chip and derives one from the name when none is set; it has no
106form for setting one yet.
107
108Issue, MR and release bodies, and their comments, carry the markup they
109were written in — =--format md|org= on create, comment and edit, stored
110alongside the text so changing a preference later cannot reinterpret
111prose that already exists. Every surface *renders* the stored format;
112the =no= above is the absence of a picker on the web form and in the iOS
113composer, both of which write markdown. Diff-line comments have no
114format column and are always markdown.
115
116* Repositories
117
118| capability | cli | web | ios |
119|-----------------------------+-----+-----+-----|
120| browse files | yes | yes | yes |
121| read a file | yes | yes | yes |
122| commit log | yes | yes | yes |
123| commit log at a ref | yes | yes | yes |
124| one commit with its patch | yes | yes | yes |
125| blame | yes | yes | yes |
126| search file contents | yes | yes | yes |
127| compare two refs | yes | yes | no |
128| branches and tags | yes | yes | yes |
129| wiki (read) | yes | yes | yes |
130| download an archive | yes | yes | n/a |
131| edit a file | yes | yes | yes |
132| create | yes | yes | yes |
133| pin | yes | yes | yes |
134| watch, mute | yes | yes | no |
135| settings, protection | yes | yes | yes |
136| topics, website | yes | yes | yes |
137| visibility | yes | yes | yes |
138| archive (read-only flag) | yes | yes | yes |
139| release list, show | yes | yes | yes |
140| release create, edit | yes | yes | yes |
141| build list | yes | yes | yes |
142| build show (one build) | yes | yes | yes |
143| build log | yes | yes | yes |
144| build jobs | yes | yes | yes |
145| build trigger | yes | yes | yes |
146| build cancel | yes | no | no |
147| dependency checks on/off | yes | yes | no |
148| dependency status | yes | no | no |
149| delete, transfer | yes | no | no |
150| release delete | yes | no | no |
151
152No row is web-only any more. Blame, file editing, log at a ref,
153archive, the public listing and the wiki were all in that state — a
154handler reading git or the store directly instead of dispatching a
155command — until krz/gitbay!99, !101 and !102 gave them commands.
156
157=build cancel= withdraws a queued build, or ends a running one: the
158server closes the runner's log session and the runner kills the step
159within a couple of seconds. Cancelling a duplicate of a commit that
160already passed the job puts that result back on the commit. No button
161on the build page yet.
162
163Dependency checks are off until a repository's admin turns them on: the
164check tells a public registry what the repository depends on. =repo deps
165status= lists what is behind and has no web view because the report
166itself is an issue the worker opens, rewrites and closes, which every
167surface already reads.
168
169The wiki row covers reading. Editing a wiki is a push to
170=<repo>.wiki.git= on every surface, including the web, so there is no
171edit row to have parity on.
172
173=n/a= marks a capability deliberately absent from a surface rather than
174missing from it. Archive download is =n/a= on iOS: the read API carries
175a command's stdout as a JSON string, so a gzip stream cannot survive it,
176and the app has nowhere useful to put a tarball — the brief rules out
177local git, so there is no clone, checkout or build to feed. The web's
178route stays the way to get one.
179
180A README or wiki page's org renders per surface: the web through
181go-org, the iOS client through the shared OrgSwift package
182(=krz/org-swift=). OrgSwift is held to orgo's output by the
183=krz/org-conformance= corpus — golden renderings from orgo, itself
184diffed against Emacs =ox-html= — so constructs the iOS client used to
185approximate (tables, footnotes, timestamps, heading tags, nested lists)
186now render the way the reference does. go-org is not yet on the corpus.
187
188* Discovery
189
190| capability | cli | web | ios |
191|----------------------------------+-----+-----+-----|
192| search repositories | yes | yes | yes |
193| search issues and merge requests | yes | yes | no |
194| browse all public repositories | yes | yes | yes |
195| profile page | yes | yes | yes |
196| profile about and links | yes | yes | no |
197| activity feed | yes | yes | yes |
198| command reference | yes | no | n/a |
199
200=explore= is the listing without a query; =repo search= is the one with.
201=search= is both plus the title and body of every issue and merge
202request the caller can read, over FTS5; the web serves it at =/search=
203with a field in the rail, and an anonymous visitor gets the public rows
204from the same query. =issue list --search= and =mr list --search= narrow
205one repository. What someone types is quoted term by term, so an FTS5
206operator — =c++=, =AND=, a lone quote — is a word to match and never a
207syntax error. =repo grep= remains the per-repository file-contents
208search.
209
210About text renders as markdown or org-mode per the =about_format= it
211was stored with. The iOS =Profile= decoder lists its keys explicitly,
212so it ignores =about= and =links= rather than breaking on them.
213
214=help= lists the command registry. Bare it is an index, one line per
215command, sorted. With a prefix (=help mr=) it adds each command's
216argument syntax, which is the only place flags are written down;
217=gitbay <cmd> --help= asks the server for the same thing, and =--json=
218returns ={path, summary, usage}=. No web page renders it, and a native
219client has no use for one (krz/gitbay#57).
220
221* Accounts
222
223| capability | cli | web | ios |
224|-----------------------------+-----+-----+-----|
225| SSH keys: list, add, remove | yes | yes | yes |
226| PGP keys: list, add, remove | yes | yes | yes |
227| email add and verify | yes | yes | yes |
228| dashboard aggregate | yes | yes | yes |
229| notification inbox | yes | yes | no |
230| API token mint | yes | no | no |
231| account export bundle | yes | no | no |
232| profile set | yes | no | no |
233| request a login link | n/a | yes | no |
234
235Notifications land in an inbox row per recipient whether or not the
236instance sends mail, and mail is the second half when SMTP is
237configured. =notifications list= reads it, unread by default;
238=notifications read <id>... | --all= clears it; the dashboard and the
239web rail carry the unread count. =repo watch= adds you to a
240repository's notifications and =repo unwatch= mutes it, and a mute wins
241over owning the repository or having written the thread.
242
243A login link is requested from the login page by username or verified
244address, and arrives by mail: it works once and expires in fifteen
245minutes. The row is =n/a= for the CLI because a terminal with a
246registered key runs =web login=, which mints a link directly and needs
247no mail. It exists because an account with no SSH key had no way into
248the web at all (krz/gitbay#155). The page offers the form only when the
249instance has SMTP configured; there is no separate switch. The response
250never says whether the account exists.
251
252=profile set= carries description, website, about and links. It is not
253=SSHOnly= — nothing about a bio is a credential, and the JSON API runs
254it — but no surface has ever offered a form, so the =no= above is
255missing UI rather than a rule.
256
257* Organizations
258
259| capability | cli | web | ios |
260|---------------------------+-----+-----+-----|
261| read members and teams | yes | yes | yes |
262| members add, remove, role | yes | yes | yes |
263| teams create, delete | yes | yes | yes |
264| team members | yes | yes | yes |
265| team repo grants | yes | yes | yes |
266| create, rename, delete | yes | no | no |
267
268* Pagination
269
270=issue list=, =mr list=, =repo list=, and =feed= take =--limit <n>=
271and =--cursor <c>=. Cursors are opaque; each page carries the next
272one. Without the flags a list stays complete, so existing scripts are
273unchanged. The web pages the issue and merge request lists at fifty
274with the same cursors; iOS pages with them too.
275
276* SSH only, by design
277
278Build secrets, mirror configuration and tokens, custom domain claims,
279API token minting, deploy keys, account and instance administration. Deleting or transferring a repository is also
280CLI-only: both want a typed confirmation, not a button.
281
282These are the only rows where a =no= is intended. Everywhere else a
283=no= is work outstanding, and =n/a= means a surface cannot usefully
284carry the capability at all — see the archive note above.