-
Notifications
You must be signed in to change notification settings - Fork 34
Skip push CI for most branches #564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Do you plan to do this in the other repos, e.g. I personally don't find it too expensive/slow (especially with |
Would @ctz's suggestion of adding |
I don't think it would. It's even more friction than having to name your branch correctly IMO because you can't say "run all the workflows" you have to do it both per-push, and per-workflow. The drop-down to select the branch to run is also a bit annoying in that it doesn't sort by recently pushed (If I remember right). I'm not strictly opposed to using the branch name approach if I'm in the rough here, but I would prefer it be consistent between rustls org repos if we can swing it. |
Yes, I can probably do this for the other repos -- agreed on the value of consistency. Do you prefer using |
No strong preference here. |
My impression is that the common practice of running CI for both
push
andpull_request
can be pretty expensive/slow while adding almost no value. Restrict branch CI tomain
and branches prefixed withrel-
orci/
.