As mentioned in Gitlab's excellent summary of the most important changes in Git v2.54, there is now a git repo structure command, intended to replace git sizer (without the heavy price that comes from Go's runtime being bundled into the executable).
This was the same intention for the git survey command that we added here and try to get to some maturity before upstreaming it. Now that upstream Git has their own command for that, we should consider what gaps it has as far as our usage is concerned, and move that functionality from git survey to git repo structure (or invent a new sub-command of git repo). After that, we should probably make git survey a very small shim that starts by showing a defection message and then hands off to git repo, and eventually remove the git survey command in a future Microsoft Git version.
As mentioned in Gitlab's excellent summary of the most important changes in Git v2.54, there is now a
git repo structurecommand, intended to replacegit sizer(without the heavy price that comes from Go's runtime being bundled into the executable).This was the same intention for the
git surveycommand that we added here and try to get to some maturity before upstreaming it. Now that upstream Git has their own command for that, we should consider what gaps it has as far as our usage is concerned, and move that functionality fromgit surveytogit repo structure(or invent a new sub-command ofgit repo). After that, we should probably makegit surveya very small shim that starts by showing a defection message and then hands off togit repo, and eventually remove thegit surveycommand in a future Microsoft Git version.