Explore >> Select a destination
|
You are here 
|
www.blopig.com | ||
| | | | |
blog.bloomca.me
|
|
| | | | | The blog of Seva Zaikov | |
| | | | |
www.lazy-electron.com
|
|
| | | | | I tend to use git from the command line frequently. There's a useful feature to reduce repetitive work called git aliases: | |
| | | | |
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. | |
| | | | |
mikecoats.com
|
|
| | | A common time-saving 'hack' of mine when building 'new-but-related-to-old' projects is to fork an existing code base and use it as the boot-strap for the new project. GitHub, however, does not provide the functionality on their website to fork your own project; you can only fork other people's projects. Here's how to work around that. | ||
