Explore >> Select a destination
|
You are here 
|
www.matsimitsu.com | ||
| | | | |
rmrz.ph
|
|
| | | | | I just wanted my git log graphs to have less noise | |
| | | | |
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. | |
| | | | |
haacked.com
|
|
| | | | | A git alias to clean up gone branches. Even ones that have been squashed and merged. | |
| | | | |
wittchen.io
|
|
| | | When you fork GitHub repository, you usually want to have your fork up to date with the original repository. You can update your fork in a few easy steps. Just look at the following example of the Git commands: Add the remote, call it upstream: git remote add upstream https://github.com/whoever/whatever.git Fetch all the branches of that remote into remote-tracking branches, such as upstream/master: git fetch upstream Make sure that you're on your master branch: | ||
