Additional resources

Blog posts

• Commits are snapshots, not diffs
• Git clone: a data-driven study on cloning behaviors
• Get up to speed with partial clone
• Bring your monorepo down to size with sparse checkout
• A deep dive into Git performance using Trace2
• Large Git repositories
• The Ingredients of a Productive Monorepo

Tools

• git-sizer (as mentioned in the detection section)

Git troubleshooting

If you ever want to see what’s happening under the covers with Git, you’re likely to want one or more of the following environment variables:

• GIT_TRACE2=1 for deep tracing
  • GIT_TRACE2_PERF offers a nice, table-oriented format which is easy to read
• GIT_CURL_VERBOSE=1 for network operations
• GIT_TRACE_PACKET=1 for packet-level tracing
• GIT_SSH_COMMAND="ssh -vvv" for SSH tracing (you can use 1, 2, or 3 vs depending on how verbose you want the output)

Engineering systems guidance

• GitHub Well-Architected

🏠 Back to front page