• Article argues pre-commit hooks are fundamentally broken due to running on working tree, not index, failing to catch unstaged changes.
• Hooks interfere with rebases, interactive commits, and external branches without hooks, requiring frequent --no-verify usage.
• Demonstrates issues via Rust fizzbuzz example: formatting fixes don't stage, existing unformatted code blocks commits, rebases fail unexpectedly.
• Recommends pre-push hooks instead: run on index, keep fast/reliable (no network/credentials), quiet, manual setup via docs.
• Additional pitfalls: slow/unreliable implementations, modifying commits, not running on stashes; prefers commits over stashes for branching.

Hacker News Discussion

• Users debate pre-commit vs. pre-push/CI: enforce in CI for reliability, use hooks to reduce churn but not guarantee (e.g., secrets in pre-push).
• Workflows vary: WIP commits common, rebase/squash before push; hooks break rebases needing full checkouts (e.g., cargo clippy).
• Editor integration preferred for formatting/linting; force consistency in teams but allow bypass for power users.
• Alternatives: git filters for formatting, jj run for future; personal setups run heavy local checks but optional for contributors.
• Defenses of pre-commit frameworks (speed, environments) countered by author; prefer CI for shared enforcement over local hooks.

Me parece súper importante porque así se puede ver si alguien hizo cambios después de las indicaciones o si siguió las reglas que se dieron.

Un commit es una acción en sistemas de control de versiones (como Git) que guarda los cambios realizados en los archivos de un proyecto dentro del repositorio. Es como tomar una “foto” del estado actual del código para poder revisarlo, compartirlo o revertirlo en el futuro.

maybefore, but check mainly AFTER indexing new files !

Can't annotate the comments for some reason, so I am copying the below:

The Jerk talked about getting hit by a bus, etc. I said who cares about code if a guy’s in hospital or there’s a war, we’ve got better things to worry about than a few days of lost code.

I feel the pain. I do. I understand. I get scared. I want to check in early and often, but source control isn’t your personal unlimited undo. When I look at history I don’t want to see rubbish. I want to see snapshots of working code.

Don’t hold back, and don’t go dark, but use your f’ing head. It’s far better to locally integrate multiple times per day and merge back after a few days because guess what, no surprises.

Super helpful how-to-guide for git pre-commit hooks.