I believe the SHA-1 hashes get 'translated' into SHA-256. [0] So though SHA-1 references stay in the repo, the preference is for SHA-256 hashes. But, an edge-ca

I believe the SHA-1 hashes get 'translated' into SHA-256. [0] So though SHA-1 references stay in the repo, the preference is for SHA-256 hashes. But, an edge-case like this may not get a full explanation until implementation. They go into it a bit more here. [1] Where what they mean may change depending on the transition timeline. To begin with, prefer SHA-1, but convert internally to SHA256. Output names to users in SHA-1 still. Only late in the transition begin to use the SHA256 names. However, the mode of operation can be changed by your git config. [0] https://github.com/git/git/blob/master/Documentation/technical/hash-function-transition.txt#L289 https://github.com/git/git/blob/master/Documentation/technic... [1] https://github.com/git/git/blob/master/Documentation/technical/hash-function-transition.txt#L567 https://github.com/git/git/blob/master/Documentation/technic...