- #99
- #98
- #97
- #96
- #95
- #94
- #93
- #92
Are Git Pre-Commit Hooks Good or Bad?
Thinking of Theo’s video: Pre-Commit Hooks Are Bad, there are some debates in the comments. In short, Git can trigger actions during a commit, usually used to run some CI checks. This seems like a good opportunity to intercept errors before they enter the version control system, but it can also become a barrier.
- ✅ Positive:
- Early Detection of Errors: Checks can be performed before the code enters version control, avoiding low-quality or bad code, reducing wasted time during Code Review.
- Reduced CI Pressure: Developers can detect and warn about errors locally.
- ❌ Negative:
- Over-reliance on Local Environment: The execution of hooks depends on the developer’s local environment; if the environment is not correctly configured, it may lead to inconsistent behavior.
- Impact on Developer Flexibility: Interferes with developers’ ability to experiment quickly locally, forcing the committed code to meet certain standards.
In the past, I encountered project Pre-Commit Hooks that always took about 5 or 6 seconds to run. While still acceptable, waiting for checks during frequent commits can be quite annoying. I tend to prefer CI checks and follow team’s habit.
- ✅ Positive:
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
- #48
- #47
- #46
- #45
- #44
- #43
- #42
- #41
- #40
- #39
- #38
- #37
- #36
- #35
- #34
- #33
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
- #23
- #22
- #21
- #20
- #19
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1