Commit `387fadad65`

387fadad65310039d5fd6ed675411c6c8bea040f

parent: e88e46e41d

Verified · cmc ci/build: success ci/sonar: success ci/test: success ci/vuln: success

cmc <hello@cleberg.net> · 2026-09-06 15:13 UTC

wiki: correct four stale parity rows

build cancel, profile set and the body-markup picker have web UI; the
matrix still read no, which puts phantom work in the web-parity
milestone. Review requests shipped without a row at all.

Ref #145

Layout: unified · split

.gitbay/wiki/Parity.org +18 −15

		@@ -47,7 +47,8 @@ browser-only and the iOS build screen unable to say more than the log.
47	47	\| create from a fork \| yes \| yes \| yes \|
48	48	\| retarget \| yes \| yes \| no \|
49	49	\| milestone \| yes \| yes \| yes \|
50		\| choose body markup \| yes \| no \| no \|
	50	\| request a review \| yes \| yes \| no \|
	51	\| choose body markup \| yes \| yes \| no \|
51	52	\| stacked merge requests \| yes \| yes \| no \|
52	53
53	54	Reviews and checks carry the time they last said something, and a
		@@ -72,10 +73,12 @@ does not appear in anyone's review queue. Draft is a flag rather than a
72	73	fifth state, so every =state = 'open'= rule still means what it did.
73	74	Batched review and range-diff (krz/gitbay#111) are not built.
74	75
75		Nothing asks a particular person for a review. The review queue is
76		computed from involvement — what you own, are granted, or reach through
77		an org or team — so a collaborator with write access who has not touched
78		a thread hears nothing until they do (krz/gitbay#145).
	76	=mr review request --add <user>= asks a particular person, who then
	77	carries the merge request in their queue and is notified; =--remove=
	78	withdraws the ask. Without one the queue is computed from involvement —
	79	what you own, are granted, or reach through an org or team — so a
	80	collaborator with write access who has not touched a thread hears
	81	nothing until they do (krz/gitbay#145).
79	82
80	83	Creating from a fork works anywhere the source can be typed as
81	84	=owner/name:branch=. The web's source picker offers the branches of
		@@ -100,7 +103,7 @@ reviews, since an approval was of the diff against the old branch.
100	103	\| milestone \| yes \| yes \| yes \|
101	104	\| milestone list \| yes \| yes \| yes \|
102	105	\| labels: list, colour \| yes \| yes \| no \|
103		\| choose body markup \| yes \| no \| no \|
	106	\| choose body markup \| yes \| yes \| no \|
104	107
105	108	Labels are created on the fly by =issue label --add= and managed by
106	109	=label list=, =label set <label> --color rrggbb= and =label remove=,
		@@ -113,9 +116,9 @@ Issue, MR and release bodies, and their comments, carry the markup they
113	116	were written in — =--format md\|org= on create, comment and edit, stored
114	117	alongside the text so changing a preference later cannot reinterpret
115	118	prose that already exists. Every surface renders the stored format;
116		the =no= above is the absence of a picker on the web form and in the iOS
117		composer, both of which write markdown. Diff-line comments have no
118		format column and are always markdown.
	119	the web's create forms offer the choice, and the =no= above is the iOS
	120	composer, which writes markdown. Diff-line comments have no format
	121	column and are always markdown.
119	122
120	123	* Repositories
121	124
		@@ -148,7 +151,7 @@ format column and are always markdown.
148	151	\| build log \| yes \| yes \| yes \|
149	152	\| build jobs \| yes \| yes \| yes \|
150	153	\| build trigger \| yes \| yes \| yes \|
151		\| build cancel \| yes \| no \| no \|
	154	\| build cancel \| yes \| yes \| no \|
152	155	\| dependency checks on/off \| yes \| yes \| no \|
153	156	\| dependency status \| yes \| yes \| no \|
154	157	\| delete, transfer \| yes \| no \| no \|
		@@ -162,8 +165,8 @@ command — until krz/gitbay!99, !101 and !102 gave them commands.
162	165	=build cancel= withdraws a queued build, or ends a running one: the
163	166	server closes the runner's log session and the runner kills the step
164	167	within a couple of seconds. Cancelling a duplicate of a commit that
165		already passed the job puts that result back on the commit. No button
166		on the build page yet.
	168	already passed the job puts that result back on the commit. The build
	169	page carries the button while a build is still cancellable.
167	170
168	171	Dependency checks are off until a repository's admin turns them on: the
169	172	check tells a public registry what the repository depends on. =repo deps
		@@ -239,7 +242,7 @@ client has no use for one (krz/gitbay#57).
239	242	\| notification inbox \| yes \| yes \| no \|
240	243	\| API token mint \| yes \| no \| no \|
241	244	\| account export bundle \| yes \| yes \| no \|
242		\| profile set \| yes \| no \| no \|
	245	\| profile set \| yes \| yes \| no \|
243	246	\| request a login link \| n/a \| yes \| no \|
244	247
245	248	Notifications land in an inbox row per recipient whether or not the
		@@ -261,8 +264,8 @@ never says whether the account exists.
261	264
262	265	=profile set= carries description, website, about and links. It is not
263	266	=SSHOnly= — nothing about a bio is a credential, and the JSON API runs
264		it — but no surface has ever offered a form, so the =no= above is
265		missing UI rather than a rule.
	267	it — and the account settings page has the form; the =no= above is the
	268	iOS client.
266	269
267	270	* Organizations
268	271

Commit 387fadad65

Commit `387fadad65`