← Back to context

Comment by wpearse

7 years ago

Thanks. Not the address with the WiFi garage thankfully.

I was actually thinking "better not commit that" ... before, y'know, I committed it :/

8 comments

wpearse

Reply
nothrabannosir  7 years ago

I got just the thing for you:

https://gist.github.com/hraban/10c7f72ba6ec55247f2d

Every time you write some code you need to remember removing before commit, surround it with a comment containing "NOCOMMIT". With this script as a pre-commit hook, git will echo an error message and fail.

E.g.:

  print("debug: ", myval)

becomes:

  print("debug: ", myval) # NOCOMMIT

I end up relying on this every day I program. Can't go back.

  • wpearse  7 years ago

    Thanks! I'm not sure how easy it would be to put the git hook on all my machines though? I have a collection of laptops (and one desktop) that I work on and I often don't use the same machine for a few weeks :-/

    I ended up using a "env.h" file... is there a C-equivalent of the PHP (?) .env file?

jimktrains2  7 years ago

git add -p

It will let you approve each hunk in a file to commit or not.

git commit -e -v

Will force you to edit the commit message and in the editor show you the diff of the commit against HEAD.

  • Drdrdrq  7 years ago

    Thank you! I use 'git add -p' all the time, but didn't know the trick with commit. I am a sucker for nice commits so I will check every commit's diff multiple times. When I don't, I usually end up including pieces of code which is not ready yet, which is meant for debugging,...