3 ms·
Don't the tests just run on the branch before the merge? If so, you wouldn't actually see the failure until after you merge.
by russell_h 12y ago
Don't the tests just run on the branch before the merge? If so, you wouldn't actually see the failure until after you merge.
- caust1c 12y agoYou can do either. Or both if you really want. $ git ls-remote From https://github.com/cyaninc/git-fat.git 4c86c39bb5fca55a692d11680ed62fd5cb183921 refs/pull/14/head cb850f9d0bd09f8bb903e1c5959cef24ceb51695 refs/pull/14/merge The merge ref is what the code would be if you merged it.
- masklinn 12y ago> Don't the tests just run on the branch before the merge? The merge button is only green if github could generate a merge commit, and that merge commit is made available. You can run your tests on either the branch before merge or the branch after merge, as you prefer. You may want to do both and have the former block the latter: the merged head is going to change (and require a re-test) any time the target branch gets a new commit, no point in wasting cycle if the branch's own tests don't pass in the first place.