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

QA/Execution/Web Testing/Automation/github (view source)

425 bytes added , 28 April 2011

no edit summary

169

edits

@@ 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.
-# 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 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
 When done and you want to delete the remote branch do
-* ''git push origin :some-new-test''
+*''git push origin&nbsp;:some-new-test''
 That deletes the remote copy in your Github.
+<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>