Explore >> Select a destination
|
You are here 
|
chambers.io | ||
| | | | |
blog.foletta.net
|
|
| | | | | ||
| | | | |
www.integralist.co.uk
|
|
| | | | | Introduction General Concept Subcommands: Porcelain and Plumbing The .git directory References and Objects References The HEAD reference Subcommands and References Detached HEAD Object Types Snapshots, Not Differences Tags Remotes Introduction There are many version control systems, but git is undoubtedly the most popular, and regularly used, thanks to online social platforms such as GitHub and GitLab. Yet, it is a tool that is still vastly misunderstood and feared. In this post I aim to take a look at s... | |
| | | | |
kennyballou.com
|
|
| | | | | A backwards introduction to the information manager from hell | |
| | | | |
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. | ||
