2 ms·
We did this with CircleCI by just ticking the "PR branches must be up to date" box in GitHub. It's more a Git provider thing than a CI thing.
by robertlagrant 4y ago
We did this with CircleCI by just ticking the "PR branches must be up to date" box in GitHub. It's more a Git provider thing than a CI thing.
- strken 4y agoYou run into problems keeping branches up to date manually with bigger teams, because every time a PR lands on main it requires everyone else with a PR up to merge main back in. If the CI handles this automatically it saves a lot of time.
- robertlagrant 4y agoFair enough, but if you have lots of branches, won't the CI be constantly rerunning as PRs are merged? Or is that the intended behaviour? I would imagine CircleCI, that bills per-minute of CI, might like that, but its customers might not :)