Inspect a file at a commit

I need to inspect config/cache.go as it was in commit 8f3b2a4. Show the file contents at that commit, note the function changes compared to HEAD, and confirm whether the timeout constant is 30 or 20 seconds in that version.

Before I forward the snapshot of config/cache.go at commit 8f3b2a4 to the ops lead, make it easy for them: show only the function bodies that changed, highlight lines where the timeout or buffer sizes differ from main, and add a one-line explanation of why the change matters to deployment stability.

Ops claims we increased the cache timeout in the last commit, but I’m not sure whether that change landed in 8f3b2a4 or later. I can pull the file at that commit but don’t know what diff to trust. What’s the fastest way to verify the exact value and who should I ping on Slack if the value differs from our deployment manifest?

During incidents we repeatedly spend time confirming which file version is deployed and which commit introduced a config change. How should we change our workflow so engineers can answer "what is running" in under five minutes? Recommend one concrete habit, one small tool or script, and one guardrail to adopt this quarter.