What did you do before the bug happened? (Steps to reproduce your issue) Tree-less git partial clone: git clone --filter=tree:0 https://... Remove the promisor to prevent retrieving more objects: git config --local --unset remote.origin.promisor Git show of a fetched commit with limited metadata fields requested: git show --no-patch --format=%ae abc123 What did you expect to happen? (Expected behavior) I expect to get the metadata I requested from the commit, since it is available in the retrieved commit object What happened instead? (Actual behavior) I get an error attempting to read the tree for the parent of the commit specified: fatal: unable to read tree (abcdef1234567890) What's different between what you expected and what actually happened? I expected the command to output the requested metadata, since there is no need to read the parent commit, much less the parent's tree object, in order to provide the required data. Anything else you want to add: Note that the data is fully accessible without error using git cat-file or git log e.g., git log -n 1 --format=%ae abc123 Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.47.2 cpu: x86_64 no commit associated with this build -- Bob Bell Distinguished Member of Technical Staff Dell | ISG TechOps Robert.Bell@xxxxxxxx Internal Use - Confidential