Explore >> Select a destination
|
You are here 
|
initialcommit.com | ||
| | | | |
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: | |
| | | | |
yasoob.github.io
|
|
| | | | | ||
| | | | |
www.integralist.co.uk
|
|
| | | | | I thought I would get down in a blog post the different Git commands and tips that I find really useful, because every now and then it seems I need to refer back to these notes (which up until this point have been in a txt file in my Dropbox) if I've not used a particular command in a while. Hopefully you'll find them useful too. Show where Git is installed Show the Git version installed Update your global user details Set-up a global ignore file Adding all files (inc. | |
| | | | |
nathanrosenquist.com
|
|
| | | [AI summary] A guide detailing the GitHub pull request workflow, including steps for forking, cloning, tracking upstream repositories, developing features, merging updates, and creating pull requests. | ||
