We went through a CI scenario documented in open source
- create pull request built by CI code change 1 by deanhiller · Pull Request #15 · deanhiller/webpieces · GitHub
- create pull request built by CI pull request 2 to demonstrate conflict by deanhiller · Pull Request #16 · deanhiller/webpieces · GitHub
together these would fail, but they succeed fine independently. We then click ‘merge pull request’ BUT this does NOT GOT THROUGH CI!!! - UGH. Clicking merge pull request on #2 would have failed and been rejected and not put on master.
My Question is thus:
Can we make it so merge pull request triggers CI but does NOT merge changes into master since we have the CI system do the merge to master IF the build passes?
Today, we do not and cannot use pull requests because it allows master to break. We operate on never allowing master to be broken by only letting CI merge into master after a working build.