| 42 | As you make changes to this branch, note they will all be local to your working directory until you push those changes into the central repo. This means that if you were to delete your directory, your branch (and all of its changes) would cease to exist (i.e. no copy of it is present in the central repo until you push). |
| 43 | |
| 44 | When you are ready to push these changes to the repo, you would give the command, |
| 45 | |
| 46 | {{{ |
| 47 | git push |
| 48 | }}} |
| 49 | |
| 50 | This pushes (i.e. copies) your current working branch into the central repo. So if you are working on *your_new_branch, then it will push a copy of your_new_branch into the repo. |
| 51 | |
| 52 | Now, the procedure for pushing changes into the development branch goes as follows. Once your changes are ready to go into the dev branch, you want to switch back to the development branch and update it so that your changes are going to be merged with the ''newest'' version of the dev branch. You do this with, |
| 53 | |
| 54 | {{{ |
| 55 | git checkout development |
| 56 | git pull |
| 57 | }}} |