Re: [PATCH v2 1/2] CI: limit GitHub Actions to designated branches

Jeff King [off-list ref] writes:

On Mon, May 04, 2020 at 05:15:44PM -0600, Taylor Blau wrote:

quoted

quoted

If this is only a reaction to what I said earlier (i.e. "building
everything in github.com/gitster/git/ has no value to me"), then I
suspect it may be an over-engineered solution to a problem that does
not exist, and harms people like you.  I could just go there and
turn off GitHub Actions for that repository instead.

It is a reaction to that, yes. It would be nice to have a middle-ground
where you can run Actions on the official integration branches, but
contributors such as myself run Actions on *every* branch of their fork.

The problem is that there is no way for people to _not_ run on every
branch of their fork, then. It is either every branch or no branches.

OK.

.... I don't like it, but I don't see any other way to let people
choose some branches but not others (that doesn't involve a one-line
yaml change at the beginning of every branch, which is an even higher
burden).

True, and having to mark a commit object with "do not run CI on this",
which is what I heard Travis does, is even worse.