| 91 | |
| 92 | == Following the development == |
| 93 | |
| 94 | As changes get pushed into the repository, you'll want to keep up with them. You can bring your local working copy up-to-date with: |
| 95 | |
| 96 | {{{ |
| 97 | svn update /srv/ir |
| 98 | }}} |
| 99 | |
| 100 | == Committing changes == |
| 101 | |
| 102 | The above setup gives you the ability to follow the course of development and to make changes to your working copy. If you've made changes that you think should be part of the main development branch, you'll need a commit access to the svn repository. If you don't have that access already, [/newticket open a ticket] requesting access to the MF/PL SVN repo. You'll need an SSH key for this. Once you've been granted access, switch your local working copy over to access the repository via ssh instead of https: |
| 103 | |
| 104 | {{{ |
| 105 | cd /srv/ir |
| 106 | svn switch --relocate https://svn.mayfirst.org/mfpl/trunk/ir svn+ssh://mfpl@svn.mayfirst.org/trunk/ir |
| 107 | }}} |
| 108 | |
| 109 | Now you can commit your changes like this: |
| 110 | |
| 111 | {{{ |
| 112 | cd /srv/ir |
| 113 | svn commit |
| 114 | }}} |
| 115 | svn will pop up an editor for you to write notes about the changes you're making. This helps everyone else (and yourself, two months from now!) understand the intent behind the changes. |