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 | ||
# 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 | ||
Then do the Github pull request as you have already. | Then do the Github pull request as you have already. | ||
Then once the pull request has been completed do | Then once the pull request has been completed do | ||
* ''git merge some-new-test'' | *''git merge some-new-test'' | ||
This merges in your changes to your local master | This merges in your changes to your local master | ||
When done and you want to delete the remote branch do | When done and you want to delete the remote branch do | ||
* ''git push origin :some-new-test'' | *''git push origin :some-new-test'' | ||
That deletes the remote copy in your Github. | That deletes the remote copy in your Github. | ||
<br> | |||
If your project has files that have sensitive information, like user-names & passwords then this is how you avoid committing those files to GitHub repository: | |||
1. In your tests folder path:<br> git add *.py<br> This will add all .py files to staging are (including the sensitive file)<br> | |||
Revision as of 18:18, 28 April 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
- git add test_that_breaks_the_world.py
- git commit -m 'You need this amazing-ness'
- git push origin some-new-test
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.
If your project has files that have sensitive information, like user-names & passwords then this is how you avoid committing those files to GitHub repository:
1. In your tests folder path:
git add *.py
This will add all .py files to staging are (including the sensitive file)