Affected files: .obsidian/app.json .obsidian/graph.json .obsidian/plugins/obsidian-omnivore/data.json .obsidian/plugins/update-time-on-edit/data.json 01. Projects/Fuuka/Outline.md 01. Projects/Juuno/Outline.md 01. Projects/Renuncia/Renuncia.md 02. Areas/Dotfiles/dotfiles tasks.md 02. Areas/Escape Latam/Canada.md 02. Areas/Escape Latam/Comparación de Paises.md 02. Areas/Escape Latam/Escapar de Latam.md 02. Areas/Escape Latam/New Zeldand.md 03. Resources/Development/Feature shipment checklist.md 03. Resources/Development/Fix messy commits.md 03. Resources/Development/Git.md 03. Resources/Development/Iframes.md 03. Resources/Development/Revert old changes in a codebase.md 03. Resources/Development/Search for a bug.md 03. Resources/Notetaking/Habits.md Read Later/2024-02-12 - Debouncing in JavaScript – Explained by Building Auto-Complete Functionality in React.md notes/Git.md
9 lines
No EOL
365 B
Markdown
9 lines
No EOL
365 B
Markdown
---
|
|
created: 2024-02-20 11:35
|
|
updated: 2024-02-20 11:37
|
|
---
|
|
# Buscar cuando un bug se introdujo
|
|
|
|
## Utilizar `git bisect`
|
|
|
|
`git bisect` hará un _"binary search"_ entre 2 commits, dejandonos señalar si este commit es _"bueno"_ (no tiene el bug) o _"malo"_ (tiene el bug), permitiendo encontrar el commit que introdujo el bug y facilitar encontrar la causa de este. |