Explore >> Select a destination
|
You are here 
|
jvns.ca | ||
| | | | |
kennyballou.com
|
|
| | | | | A backwards introduction to the information manager from hell | |
| | | | |
chambers.io
|
|
| | | | | So far this week we've talked about what Git is and how to use it. If you're anything like me, you want to know how things work under the hood. When you first learn Git it can seem like magic...but it also seems like something that can easily break. Or something that works by pure demonic byte voodoo. One of the best things Git does is allow you to write code with confidence - fear not about breaking things or losing files. They're always recoverable. To feel confident, it helps to know how things work. | |
| | | | |
www.integralist.co.uk
|
|
| | | | | Introduction General Concept Subcommands: Porcelain and Plumbing The .git directory References and Objects References The HEAD reference Subcommands and References Detached HEAD Object Types Snapshots, Not Differences Tags Remotes Introduction There are many version control systems, but git is undoubtedly the most popular, and regularly used, thanks to online social platforms such as GitHub and GitLab. Yet, it is a tool that is still vastly misunderstood and feared. In this post I aim to take a look at s... | |
| | | | |
blog.danskingdom.com
|
|
| | | Developers often have tens or hundreds of Git repositories on their machines. When we are done with a project, we often forget to clean up the repository, leaving temporary files like build artifacts, logs, packages, modules, and other files taking up valuable disk space. | ||
