Explore >> Select a destination
|
You are here 
|
www.brandonpugh.com | ||
| | | | |
blaster.ai
|
|
| | | | | Helping e-commerce startups grow | |
| | | | |
fnordig.de
|
|
| | | | | Personal website of Jan-Erik Rediger | |
| | | | |
vlad.website
|
|
| | | | | Sometimes, you want to add some code to test something out, but you definitely want to make sure you don't git commit it. Of course, you should always check the output of git diff before you make a commit (you do, right?), but if you have a lot of changes things can slip through the cracks. A solution is to write a comment containing a string such as "nocheckin": function do_stuff() { printf("hello!!! testing!!!\n"); // nocheckin call_important_thing(); call_other_thing(); } Then, you need to set git up such that it refuses to make a commit if it detects the "nocheckin" string anywhere in your changed files. Here's how to do it. | |
| | | | |
daily.dev
|
|
| | | [AI summary] A tutorial explaining how to use Git bisect to efficiently identify the specific commit that introduced a bug in a codebase. | ||
