/explore
|
You are here 
|
blaster.ai | ||
| | | | |
third-bit.com
|
|
| | | | | [AI summary] A developer shares a troubleshooting problem with a pre-commit hook failing to prevent commits in Git and discusses the necessary knowledge for someone new to scripting to debug the issue. | |
| | | | |
hjr265.me
|
|
| | | | | Git has this great feature that I think is well-known but under-used. I am talking about Git hooks. With Git hooks, you can run scripts during different Git actions. Like this one: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 #!/bin/sh GOFILES=`git diff --name-only --cached | grep -e '.go$' | grep -ve 'vendor/'` UNFMTFILES=() for f in $GOFILES; do if [ -n "`gofmt -l -s . | |
| | | | |
www.brandonpugh.com
|
|
| | | | | TLDR: Git hooks are an awesome way to automatically verify your code as you commit your changes I'm sure we've all been there where we accidentally committed a change that we were supposed to undo or wasn't ready to be pushed and don't realize it until the build breaks or QA finds a bug. The first step I take to avoid committing anything unintentionally is instead of just running git add -A I make sure to review all the changes in the files I'm potentially committing. This is where a graphical tool like Gitk or SmartGit comes in handy as they allow you to click on your modified files and easily view a diff and then select which changes to stage. Unfortunately changes still slip through as happened to me yesterday when a change of mine got pushed all the way ... | |
| | | | |
www.learnitguide.net
|
|
| | | Learn how to install Docker on Ubuntu 22.04 step by step with commands, explanation, and verification. Perfect for beginners. | ||
