Hacker News Reader

What if you still have too many pull requests per day, compared to the time it takes to run CI? For example if you get 10 PRs a day but CI takes 3 hours?

View on HN

Not sure if this does the same thing, but bors[1], another implementation of this concept, will batch together multiple PRs into a single CI run and follow a git-bisect-like workflow to identify the bad PR if a batch fails.

[1] https://github.com/bors-ng/bors-ng

Best way is to batch your PRs in a single CI run. That saves CI time and increase your throughput.

It does not seem GitHub merge queue supports this, but some merge queues do support this.

(Julien from Mergify)

Reply on news.ycombinator.com