👋 How do I get GitHub Actions to build pull requests in a stack against a merge SHA that’s equivalent to the the final merge commit (assuming trunk doesn’t move on)? The first PR in a stack when using GitHub Actions will run “correctly” on a tree which is equivalent to a merge, but subsequent ones (i think?) won’t, because they would only run on a merge between each stack, rather than going all the way through!
This usually happens for free because GitHub generates this merge_commit_sha in the background, I guess the Q is, from a stacked branch, is there a nifty way that Graphite creates a merge commit that includes the changes from the target through to the current stacked branch?