/explore
|
You are here 
|
gist.github.com | ||
| | | | |
cupano.com
|
|
| | | | | My Blog Posts. Contribute to joecupano/blog development by creating an account on GitHub. | |
| | | | |
www.github.com
|
|
| | | | | my blog, with astro. Contribute to Krayorn/blog development by creating an account on GitHub. | |
| | | | |
fireburn.ru
|
|
| | | | | ||
| | | | |
citizen428.net
|
|
| | | 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: | ||
