| ▲ | conradludgate an hour ago | |
In my experience, it's a monorepo problem. We have a monorepo at work and the CI only runs a minority of tests prior to merging, and then reverts bad commits later. It can take a few hours until every test has run including your commit. I don't know enough about the setup to know how it decides to run what tests though | ||
| ▲ | inigyou 32 minutes ago | parent | next [-] | |
Yeah that's true. It becomes O(N^2) with one factor of N being the number of commits to the repo, and another factor being the amount of CI stuff you do every time the repo changes. | ||
| ▲ | orf 32 minutes ago | parent | prev [-] | |
How does it handle conflicts during reverting? If another merge depends on a change, and that change causes a failing/broken test, does it revert both? | ||