In this workflow, I don't think it's meant to have the same
SHA1 digest. It's a workflow that's very much designed for a handful of core contributors (who have direct repository access) and gatekept one-off patches.
Some other accepted git workflows, like rebasing onto master, or even adding a "committed-by" or "signed-off-by", don't preserve SHA1 hashes either, and it seems you don't really need that property outside of closely collaborating cliques.