QA/Execution/Web Testing/Automation/github

From MozillaWiki
< QA‎ | Execution‎ | Web Testing‎ | Automation
Revision as of 18:18, 28 April 2011 by Vish moz (talk | contribs)
Jump to navigation Jump to search

If you are working with a Fork of one of repositories, please follow the steps below as it makes processing GitHub Pull Requests easier.

  1. git branch some-new-test
  2. git add test_that_breaks_the_world.py
  3. git commit -m 'You need this amazing-ness'
  4. 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)