torspec (and other repos?) forks with disabled "use shared runners" setting
As far as we can tell:
- In the past, the
tpo/core/torspec
repo had "use shared runners" disabled in the repo gitlab config - Now it has CI, and the shared runners are enabled.
- By default, users who forked the tree in the past don't have "use shared runners"; nor do they have any of their own runners, obviously. So the CI for them is broken.
- The effect is that when we get MRs from those users we have to ask them to fiddle with obscure gitlab settings.
- It appears that other users'
torspec
clones are probably affected. At a guess, this problem will arise a further 10-20 times fortorspec
MRs. - Possibly repos other than
torspec
may be affected.
It would be desirable to identify the users who:
- Don't have "use shared runners"
- Don't have any runners of their own (as a proxy for detecting anyone who might have deliberately disabled the shared runners, although we don't think there are any)
and set their "use shared runners" flag.
I'm told that this could be done with a script (great). I'm filing this ticket to note down our discoveries and intentions, pending someone having time to work on it. (Neither I, nor the TPA team, do, right now.)