/explore
|
You are here 
|
dylanpaulus.com | ||
| | | | |
jackharner.com
|
|
| | | | | Getting Started with Git: Installing and Cloning Repositories from GitHub This guide will help you get Git installed on your computer, clone your... | |
| | | | |
blog.kulman.sk
|
|
| | | | | When working on iOS applications, I often find myself in situations where I need to develop a new feature while simultaneously fixing a bug. This can be challenging to manage, especially when the changes for the feature and the bug fix overlap. Developers have different approaches to handle this: Stashing changes Creating temporary commits Cloning the repository twice While these methods work, they are not ideal. Recently, I discovered a better solution. | |
| | | | |
nicolaiarocci.com
|
|
| | | | | The official Git documentation presents the following example as a valid use-case for the worktree command: You are in the middle of a refactoring session and your boss comes in and demands that you fix something immediately. You might typically use git-stash1 to store your changes away temporarily. However, your working tree is in such a state of disarray (with new, moved, and removed files and other bits and pieces strewn around) that you don't want to risk disturbing any of it. (source) | |
| | | | |
initialcommit.com
|
|
| | | In this article, you will learn how to create a new Git repository, configure it, and commit changes to it. | ||
