Parity: attaching a runner is n/a on iOS !356

merged merged by cmc on 2026-09-10 00:14 UTC · krz/gitbay:parity-runners-ios into main

1 file changed, +6 −2

Layout: unified · split

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