Confirmed users
182
edits
Web Testing/Automation/CodeReviewProcess/Repository setup: Difference between revisions
Web Testing/Automation/CodeReviewProcess/Repository setup (view source)
Revision as of 18:25, 4 August 2011
, 4 August 2011→Case 2: Repository for you own work: WIP
| Line 28: | Line 28: | ||
2. Once you cloned your repository, you might want to create a new branch for your changes. This way, you keep your main branch clean and prevent merge conflicts from happening.<br><code><nowiki>#Create a new branch for your changes and switch to it immediately:</nowiki><br> git checkout -b stuffIWillBeWorkingOn</code> | 2. Once you cloned your repository, you might want to create a new branch for your changes. This way, you keep your main branch clean and prevent merge conflicts from happening.<br><code><nowiki>#Create a new branch for your changes and switch to it immediately:</nowiki><br> git checkout -b stuffIWillBeWorkingOn</code> | ||
3. Now that you switched to that branch, you might want to do whatever work comes to your mind, write a new test, improve an already existing test or do other changes to the test files. Once you're done, execute the <code>git status</code> command to see which files from your current branch were changed (if you can't remember, which I normally can't :-) ). Once you know which files to commit, you execute the<br><br><code>git commit <filename_1> <filename_2> <filename_n> -m "This is a very meaningful message describing your changes"</code><br><br> | |||
command. | |||