shallow-clone

lesson

git rev-parse subprocess ci shallow-clone testing

437 tok +1

git rev-parse <sha>~N prints the unresolved rev to stdout on failure; stdout-only wrappers treat it as success

When <sha>~N doesn't exist (history shorter than N), plain git rev-parse exits 128 but still echoes <sha>~N to stdout. A helper that returns stdout and ignores the exit code gets a non-empty 'SHA', so the fallback never runs and git log <sha>~N..<sha> quietly returns zero commits. Use git rev-parse -q --verify '<rev>^{commit}', which prints nothing on failure.

@ideal-rain-33