GitHub Action: build on push to non-master branches #28013
Conversation
sgn
changed the title
|
Doesn't this mean that a staging branch with huge changes will be unnecessarily running CI? I have a couple branches I keep around that I don't want to have CI run on... Opening a PR on your own repo is the simplest way of achieving this without spending a bunch of time running builds. |
|
We can set the ignore to pattern matching, let's say, ignore branches with name: 'wip-*' |
sgn
force-pushed
the
liquid-dsp
branch
2 times, most recently
from
ed93753
to
0ebbc55
Compare
|
I'm concerned about people who aren't aware of this new default getting lots of notifications and spending more CI time than they expect. GH is kinda stupid as well, so it will have separate CI runs for the PR and for the branch in the person's repo. Anyway, if you think this is useful (and I believe others have requested it as well), we can turn it on. As long as this doesn't impact us too much (by, say, counting the number of machines we are using by including forks), I think we can push as something experimental. |
|
Whats the liquid-dsp change? |
|
On 2021-01-18 16:10:09-0800, fosslinux ***@***.***> wrote:
Whats the liquid-dsp change?
That one was pushed out b68a299
|
|
@sgn maybe we can make CI run on branches named |
|
Yay, let's do that instead. |
See https://github.com/sgn/void-packages/actions/runs/493766269