Explore >> Select a destination
|
You are here 
|
nathanrosenquist.com | ||
| | | | |
varunbarad.com
|
|
| | | | | This is a simple guide on how to sync your fork of a git/github project with upstream changes. | |
| | | | |
mark-story.com
|
|
| | | | | As a long time open source maintainer, I occasionally have to modify pull requests made by contributors via forks. If a contributor needs help adding/fixing tests, or addressing linter errors, it is often simpler for me to modify a pull request by adding a commit to their branch. I like this workflow as I can help the contributor out, and give them the option to revise my changes as well. | |
| | | | |
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 | |
| | | | |
misha.brukman.net
|
|
| | | Useful Git aliases for streamlined workflows. | ||
