Explore >> Select a destination
|
You are here 
|
blog.keikooda.net | ||
| | | | |
tannerdolby.com
|
|
| | | | | To begin contributing to open-source software, you might want to become familiar with Git. Understanding the workflow of creating your own local copy of a repository and keeping it up to date with the upstream repository is integral to start contributing in public projects. | |
| | | | |
jinyuz.dev
|
|
| | | | | There was a pull request on GitHub and it contains a feature I wanted to test. I didn't know how to test it locally. Should I just copy the changes to my local since the changes weren't that big? But what if it was? Luckily, I found some answers by googling and decided to write it up for future reference. Git provides a command for it and here is the sample syntax | |
| | | | |
conradresearch.com
|
|
| | | | | Guide to building the Turso Golang client on FreeBSD. | |
| | | | |
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: | ||
