Explore >> Select a destination
|
You are here 
|
jvns.ca | ||
| | | | |
www.mgasch.com
|
|
| | | | | Ever wanted to contribute to an open source project but quickly got overwhelmed with git terminology? I'm glad you asked... | |
| | | | |
initialcommit.com
|
|
| | | | | A complete guide to using the git cherry pick command. | |
| | | | |
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: | |
| | | | |
ryanharter.com
|
|
| | | I recently shared how I use Git to automatically track my versions. There's quite a bit more to my git workflow than just tagging versions, though, so I'd like to dive into my git usage just a little more. One of my clients introduced me to a very popular, and useful, git branching strategy commonly called Git-Flow based on Vincent Driessen's branching model. I highly recommend reading his article, it's quite good and describes a very useful branching model. | ||
