QA/Execution/Web Testing/Automation/github: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 20: Line 20:
That deletes the remote copy in your Github.  
That deletes the remote copy in your Github.  


<br>
<br>
 
If your project has files that have sensitive information, like user-names &amp; passwords then this is how you avoid committing those files to GitHub repository:
 
&nbsp;&nbsp;&nbsp; 1. In your tests folder path:<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; git add *.py<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This will add all .py files to staging are (including the sensitive file)<br>
 
&nbsp;&nbsp;&nbsp; 2. git rm --cached sensitive_file_name<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This command will prevent the file from being committed but leave the file on your local disk<br>
 
Alternatively, just add the files that have changed so that you don't do a blanket commit and commit things that should be in a separate commit. <br>

Revision as of 09:35, 5 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.

  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.


Retrieved from "https://wiki.allizom.org/index.php?title=QA/Execution/Web_Testing/Automation/github&oldid=305751"