I suspect the best way out may be to remove the `should_ignore_subtree_split_commit` heuristic entirely.
It is mostly useful for repos that use `split --rejoin` a lot, and the check itself is slow. WDYT?

I think this sound reasonable yea. Should be sure to include a spec to capture this case going forward too ofc.
This would at least fix the breaking change, and some other heuristic could be applied in the future.

git v2.51.0 also adds --gpg-sign compatibility to subtree.
Perhaps this is what you are seeing?

Hmm, I don't think so as I'm just learning about this now.
Will give it a shot next time I have to add another component tho!