![\"Submitting](\"http:\/\/www.projectimmerse.com\/wp-content\/uploads\/2018\/07\/github-pull-request-1024x490.png\")
<\/p>\n<\/p>\n
A step by step guide on the pull request cycle. Submitting a pull request is part of a larger process in which external members can make modifications to the existing code base. <\/p>\n
Cloning involves making a copy of a git repository onto a local machine. In contrast, a fork is a cloning of one git repository to another repository.<\/p>\n
<\/p>\n
Make necessary modifications to the codebase. After this is complete, the next step is to submit a pull request. While submitting a pull request, a message is required indicating any helpful notes describing the task. <\/p>\n
Send a pull request, which is simply a request for changes. First check the Comments and Files Changed tab to verify final changes. <\/p>\n
Cloning your Fork to local machine
\nRun the following command to clone the forked repo to your local machine.<\/p>\n
# Clone your fork to your local machine
\ngit clone git@github.com:USERNAME\/FORKED-PROJECT.git<\/p>\n
Keeping your fork up to date
\nKeep your fork up to date by tracking the original \u201cupstream\u201d, to do this you\u2019ll need to add a remote. <\/p>\n
# Add ‘upstream’ repo to list of remotes
\ngit remote add upstream https:\/\/github.com\/UPSTREAM-USER\/ORIGINAL-PROJECT.git<\/p>\n
# Verify the new remote named ‘upstream’
\ngit remote -v<\/p>\n
Whenever you want to update your fork with the latest upstream changes, you’ll need to first fetch the upstream repo’s branches and latest commits to bring them into your repository:<\/p>\n
# Fetch from upstream remote
\ngit fetch upstream<\/p>\n
# View all branches, including those from upstream
\ngit branch -va<\/p>\n
Now, checkout your own master branch and merge the upstream repo’s master branch:<\/p>\n
# Checkout your master branch and merge upstream
\ngit checkout master
\ngit merge upstream\/master<\/p>\n
If there are no unique commits on the local master branch, git will simply perform a fast-forward. However, if you have been making changes on master (in the vast majority of cases you probably shouldn’t be, you may have to deal with conflicts. When doing so, be careful to respect the changes made upstream.
\nNow, your local master branch is up-to-date with everything modified upstream.
\nDoing your work<\/p>\n
Whenever you begin work on a new feature or bugfix, it’s important that you create a new branch. Not only is it proper git workflow, but it also keeps your changes organized and separated from the master branch so that you can easily submit and manage multiple pull requests for every task you complete.
\nTo create a new branch and start working on it:<\/p>\n
# Checkout the master branch – you want your new branch to come from master
\ngit checkout master<\/p>\n
# Create a new branch named newfeature (give your branch its own simple informative name)
\ngit branch newfeature<\/p>\n
# Switch to your new branch
\ngit checkout newfeature<\/p>\n","protected":false},"excerpt":{"rendered":"
Overview A step by step guide on the pull request cycle. Submitting a pull request is part of a larger process in which external members can make modifications to the existing code base. Forking Fork target repository Cloning involves making a copy of a git repository onto a local machine. In contrast, a fork is … <\/p>\n