Oh I think I see what you mean – you are suggesting adding an “–exec” to git-explode which would allow arbitrary commands to be run after the creation of each commit in each new branch, right? That’s possible, although git-explode is non-interactive and doesn’t currently work like rebase, even though splice and transplant do, so I’m not sure it makes sense at this point. That could change in the future though.

That sounds like an interesting idea – please could you give more details about the use case you have in mind for this?

Thanks for the comment. I’m not sure what you mean by “fulfill this requirement” – please could you elaborate?

If these tools work anything like rebase then the –exec option (or exec in the pick list) would be idiomatic and fulfill this requirement.

This is covered in detail in the video, but briefly a) it can transplant *into* the target branch, not just at the tip, b) it can optionally create a new branch, and c) it removes whichever commits were transplanted from the source branch.

Great idea Jeremy! That doesn’t sound too hard, but I think it should remain outside the scope of git-explode itself, because there are many different ways to do CI.