/explore
|
You are here 
|
nathanrosenquist.com | ||
| | | | |
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 |
|
| | | | | ||
| | | | |
truss.works
A git workflow that supports feature development isolation, continuous deployment, and has minimal overhead when performing common operations like branching and merging |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
sookocheff.com
This is something I often do but rarely remember the steps for. This post is intended to serve as a reminder for me and anyone else having the same question: how to add an upstream remote git repository. Start by forking the repository you are contributing to and cloning that repository to your local file system. In this example, we will use the Elasticsearch repository and assume you have cloned it locally. |
|
| | | |||
