Jeff King <peff@xxxxxxxx> writes: >> > Or since we're running a shell in a VM, we really >> > could just run "./allow-ref $refname" and let individual forks specify >> > whatever shell code they like. >> >> I presume that you are saying "checking out the tree of refs/ci/config >> and there is a program allow-ref that can tell which one to run ci on"? > > Yes, exactly. I guess a simple example implementation of allow-ref script, with a bit of instruction to tell people how to initialize a separate and otherwise empty repository with just a (possibly customized) copy of the script in it, and push its 'master' branch to refs/ci/config of their Git fork, would be a way to go, then? Sounds simple enough. Cycles to spin up a VM that adds 3 seconds latency, only to know that a branch won't need to be built, does sound like a bit unfortunate, though.
