yeah I was thinking about the latest commit on the master. I mean, it would fail if master Ci fails. It may not be so efficient. Let me check how much we can save by doing this.
BTW, we can actually have a queue (by making the build sequentially - it;s supported via GitHub Actions). We accidentally enabled this before, and it was disabled back cuz it was too slow .. - it had to be one by one. On Thu, 19 Nov 2026 at 08:16, Nicholas Chammas <[email protected]> wrote: > The main objection to this idea is that master may progress after PR CI > passes, so the build can fail silently post merge if we do not either a) > test every commit on master, or b) require that a PR pass CI *on the > latest* master before merging. > > b) is not practical without a merge queue, because PRs will constantly be > chasing a moving target. > > I am in favor of building our own merge queues. I think it’s the right > long-term approach. Happy to invest in this if there is support for the > idea. > > > On Nov 18, 2026 at 6:10:00 PM, Hyukjin Kwon via dev <[email protected]> > wrote: > >> Let me actually do a quick research and how much we can save by doing so >> >> On Thu, 19 Nov 2026 at 08:09, Hyukjin Kwon <[email protected]> wrote: >> >>> Hi all, >>> >>> To reduce the CI usage, I am thinking about skipping the CI build >>> IFF the CI passed against the latest commit in the master branch. WDYT? >>> >>
