Hacker News new | ask | show | jobs
by pavel_lishin 3479 days ago
Most CI solutions will take care of that; they'll pull in the PR, merge it locally with master, and run tests on that.
1 comments
x1798DE 3478 days ago
I can't speak to the "merge-and-run" behavior of CI, but in my experience, most of these merge conflicts arise because of a time delay between making the PR (at which point CI is run) and merging the PR. It would be quite resource intensive to re-build every PR against every new branch in master.
link
pavel_lishin 3478 days ago
> It would be quite resource intensive to re-build every PR against every new branch in master.

Depends on just how resource intensive a build is, and how often commits are made to master.

Here at work, we don't do that, but it wouldn't be a complete clusterfuck if we were to.

link