|
You are here |
www.morling.dev | ||
| | | | |
blog.piotrnalepa.pl
|
|
| | | | | In this article I'm explaining what are the most common strategies to keep your working Git branches up-to-date and to make it easy to debug the codebase. | |
| | | | |
www.integralist.co.uk
|
|
| | | | | Introduction git merge git merge --no-ff --edit git reset Force the merge commit git branch --contains Losing useful history git merge --squash git rebase git rebase --interactive git rebase --onto git format-patch Conclusion Introduction Imagine I have a master branch with one commit: 75eb1cb - (origin/master) README This is a single README.md file with the following content: - A: 1 Now imagine I have a branch from master called feat/foo and in that branch I've made 3 additional commits: | |
| | | | |
blog.bloomca.me
|
|
| | | | | The blog of Seva Zaikov | |
| | | | |
hamatti.org
|
|
| | | I love dotfiles and I love sharing. But I have this weird feeling that sharing my dotfiles is too intimate and personal. | ||