Pull Request (PR): A git workflow
Download as PDF, PPTX3 likes1,417 views
The document provides instructions for sending a pull request to a remote public repository in 3 steps: 1. Fork the remote public repo and work on a branch rather than the master branch, committing changes to that branch. 2. On GitHub, switch to your branch and send a pull request from your repo to the remote repo's master branch. 3. The remote repo will review the change and potentially merge it into their branch.
More Related Content
Similar to Pull Request (PR): A git workflow (20)
Pull Request (PR): A git workflow
- 1. You plan to send a Pull Request (PR) to a remote public repo
- 3. Download git For windows For OSX For Linux Create a git account config the global user if needed for committing git config --global user.name <YOUR NAME> git config --global user.email <YOUR EMAIL>
- 4. YOU: Fork a remote public repo (UI operation) Work on a branch (DO NOT WORK on MASTER) Commit to that branch (avoid multiple commits otherwise squash into one) On github UI from your repo, switch to your branch, send a pull request to the remote repo master unless specified otherwise Remote public repo (upstream) Review the change Merge into their branch if ok
- 5. Local (master) git clone <your forked repo origin> git remote add upstream <repo you forked from> git checkout –b <branch> git add* git add <filename> git commit –m “message” Push to your remote repo (origin) git push origin <branch>
- 6. If everything goes ok, you are safe to delete this branch, from your locale repo git push origin –delete <branch> If you want to PR later to the same remote repo Keep your master clean so you can rebase Keep your fork updated git fetch upstream Git merge upstream/master work on a branch Always work on a branch from your forked repo If your PR needs rework, commit to the same branch, then may need to squash commits