Steps when a scalar repo becomes corrupted

[hannahchiodo-msft]

• I was not able to find an open
  or closed issue matching
  what I'm seeing, including in the git-for-windows/git tracker.

Setup

• Which version of microsoft/git are you using? Is it 32-bit or 64-bit?

$ git --version --build-options

git version 2.43.0.vfs.0.0
cpu: x86_64
built from commit: b7a6ed788a205fb2c0013111d277b4c9d6ab35bd
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor–daemon

Are you using Scalar or VFS for Git?

Scalar

• Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?

$ cmd.exe /c ver

Microsoft Windows [Version 10.0.22621.3007]

• Any other interesting things about your environment that might be related
  to the issue you're seeing?
  The is in the Office Monorepo. Customer reports this happened during "routine commit and pushes".

Details

• Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other

CMD

• What commands did you run to trigger this issue?

D:\Office\src>git status
fatal: unable to read tree 774f3905006aed444504deecf77321fa8b8accd4

• What did you expect to occur after running these commands?
  Git reporting status.

• What actually happened instead?
  Above output. We would like to know what the recommended course of action is when a scalar enlistment becomes corrupted as git fsck is not supported.

• If the problem was occurring with a specific repository, can you specify
  the repository?

  • Public repo: insert URL here
  • Windows monorepo
  • Office monorepo
  • Other Microsoft-internal repo: insert name here
  • Other internal repo.