Consider the use of Git history in debugging

When someone files an issue about a bug in a project, examining Git history effectively is a critical debugging skill. But if they look at the commit that introduced the bug, they see the fix.

- [ ] How do we contain the bug in a meaningful way, while supporting appropriate examination of a project's history during the debugging process?

Start by reviewing the existing py-bugger debugging exercises and the issue's question about Git history. Determine how bug-containing behavior should work without preventing examination of project history; the work is done when the repository has an agreed, testable approach.

Written by the indexing model from the issue text.