Commit `d8b021023e`

d8b021023ea71fdbd33c7f11e6c6828fc7b9d6e1

parent: 315847fa78

Verified · cmc ci/build: success ci/test: skipped

cmc <hello@cleberg.net> · 2026-09-10 00:13 UTC

Parity: attaching a runner is n/a on iOS

The key lives on the machine that runs builds; the attach step happens
there or on the settings page. Column alignment on the row fixed.

Ref #184

.gitbay/wiki/Parity.org +6 −2

		@@ -162,7 +162,7 @@ always markdown.
162	162	\| access grants \| yes \| no \| yes \|
163	163	\| effective access \| yes \| no \| yes \|
164	164	\| webhooks \| yes \| no \| yes \|
165		\| runners attach, list, detach\| yes \| yes \| no \|
	165	\| runners attach, list, detach \| yes \| yes \| n/a \|
166	166	\| import from a remote \| yes \| no \| yes \|
167	167	\| topics, website \| yes \| yes \| yes \|
168	168	\| visibility \| yes \| yes \| yes \|
		@@ -231,7 +231,11 @@ and the app has nowhere useful to put a tarball — the brief rules out
231	231	local git, so there is no clone, checkout or build to feed. The web's
232	232	route stays the way to get one. =release asset add= is =n/a= on iOS for
233	233	the same reason from the other direction: the file arrives on stdin,
234		which the API carries as a JSON string.
	234	which the API carries as a JSON string. Attaching a runner is =n/a= on
	235	iOS for a plainer reason: the key is generated by =gitbay-runner init=
	236	on the machine that will run builds, and that machine's terminal (the
	237	command =init= prints) or the settings page is where the paste happens.
	238	A phone has neither the key nor the runner.
235	239
236	240	A README or wiki page's org renders per surface: the web through
237	241	go-org, the iOS client through the shared OrgSwift package

Commit d8b021023e

Commit `d8b021023e`