/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

www.brandonpugh.com
| | codeinthehole.com
1.4 parsecs away

Travel
| | Yet another git tips article
| | vlad.website
1.7 parsecs away

Travel
| | 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.
| | blaster.ai
2.7 parsecs away

Travel
| | Helping e-commerce startups grow
| | varunbarad.com
17.2 parsecs away

Travel
| This is a simple guide on how to sync your fork of a git/github project with upstream changes.