/explore
|
You are here 
|
jinyuz.dev | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
lirantal.com
Getting started with MEAN.io JavaScript & Node.js framework by keeping up with the git branch of development |
|
| | | | | ||
| | | | |
adam.younglogic.com
|
|
| | | | | ||
| | | | |
danielpecos.com
In a previous post, we have seen what Git is and its main characteristics. Now, we'll go more into detail about its functionality and we'll see what a usual day working with Git looks like. But before, some initial concepts: Repository: A working tree of files and directories which can be versioned, keeping track of every single modification made over the working tree, been able to move forward and backward in its history. |
|
| | | |||
