Explore >> Select a destination
|
You are here 
|
blaster.ai | ||
| | | | |
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 ... | |
| | | | |
osc.garden
|
|
| | | | | In order to keep the 'Last updated' field of posts always accurate, I automated its modification with a custom Git pre-commit hook. | |
| | | | |
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 . | |
| | | | |
wittchen.io
|
|
| | | Introduction I have my own tiny Python project called spotify-cli-linux, which is (surprise!) command line interface for Spotify desktop app on Linux. Python is not my primary programming language and I work more with Java. Nevertheless, I find this language enjoyable and useful in many cases, so I try to learn something new about it from time to time. In the beginning, I've provided instructions how to install my Python script in the system via curl and wget, which is fine, but it's not recommended and ... | ||
