Explore >> Select a destination

You are here

 danielrotter.at
git bisect and the importance of a clean history | Daniel Rotter
| | blog.piotrnalepa.pl
Git merge vs git rebase why you should avoid using Git merge to update your branches? | Piotr Nalepa - Blog webmasterski | T...
10.4 parsecs away

Travel
| | In this article I'm explaining what are the most common strategies to keep your working Git branches up-to-date and to make it easy to debug the codebase.
| | citizen428.net
10 Common Git Problems and How to Fix Them - citizen428.net
10.6 parsecs away

Travel
| | I originally wrote this article for Codementor in October 2014. It should have something for everyone, from fairly new git users to experienced developers. 1. Discard local file modifications Sometimes the best way to get a feel for a problem is diving in and playing around with the code. Unfortunately, the changes made in the process sometimes turn out to be less than optimal, in which case reverting the file to its original state can be the fastest and easiest solution:
| | vishaltelangre.com
Chasing a bad commit | Vishal Telangre
7.8 parsecs away

Travel
| |
| | techtldr.com
Private Git Repository on Any Computer - Tech TLDR;
104.0 parsecs away

Travel
| With popularity of Github and many other competing offerings, it's easy to overlook how simple it is to set up (unlimited) private repos on any network connected computer. For example, I run this blog on a cheap instance of Linode, where $5 a month get's you 20Gb SSD storage. But you don't have to pay [...]