QA/Execution/Web Testing/Automation/github: Difference between revisions
< QA | Execution | Web Testing | Automation
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
If you are working with a Fork of one of repositories, please follow the steps below as it makes processing GitHub Pull Requests easier. | If you are working with a Fork of one of repositories, please follow the steps below as it makes processing GitHub Pull Requests easier. | ||
#git branch some-new-test | #git branch some-new-test-branch | ||
#git add test_that_breaks_the_world.py | #git add test_that_breaks_the_world.py | ||
#git commit -m 'You need this amazing-ness' | #git commit -m 'You need this amazing-ness' | ||
#git push origin some-new-test | #git push origin some-new-test-branch | ||
Then do the Github pull request as you have already. | Then do the Github pull request as you have already. | ||
Revision as of 17:41, 16 May 2011
If you are working with a Fork of one of repositories, please follow the steps below as it makes processing GitHub Pull Requests easier.
- git branch some-new-test-branch
- git add test_that_breaks_the_world.py
- git commit -m 'You need this amazing-ness'
- git push origin some-new-test-branch
Then do the Github pull request as you have already.
Then once the pull request has been completed do
- git merge some-new-test
This merges in your changes to your local master
When done and you want to delete the remote branch do
- git push origin :some-new-test
That deletes the remote copy in your Github.