169
edits
QA/Execution/Web Testing/Automation/github: Difference between revisions
QA/Execution/Web Testing/Automation/github (view source)
Revision as of 18:20, 28 April 2011
, 28 April 2011no edit summary
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
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: | 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> | 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> | ||
2. git rm --cached sensitive_file_name<br> 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> | |||