This tutorial describes how you can commit and push MAR code changes on a GitLab repository (such as [ESPECES/MAR/stable](https://gitlab.uliege.be/especes/mar/stable)) from a cluster or lab machine (such as climato\.be) using a few ``git`` commands.
This tutorial describes how you can commit and push MAR code changes on a GitLab repository (such as [ESPECES/MAR/stable](https://gitlab.uliege.be/especes/mar/stable)) from a cluster or lab machine (such as climato\.be) using a few ``git`` commands.
13) Finally, if you previously pulled content from a ESPECES/MAR repository by following the [Getting the latest MAR version (code only)](mar-pull) tutorial, go to the location(s) where you did the pull operation(s) and modify the `.git/config` file (with vim or gedit) to update the `url` field. Indeed, in the previous tutorial, remote repositories were accessed through HTTP. Now, you can (and should) access them through SSH. It simply consists of replacing the ``https://`` prefix by ``git@`` and the forward slash in ``uliege.be/especes`` by a colon (``uliege.be:especes``). E.g., for the [ESPECES/MAR/stable repository](https://gitlab.uliege.be/especes/mar/stable), you should have the following lines in your `.git/config`.
13) Finally, if you previously pulled content from a ESPECES/MAR repository by following the [Getting the latest MAR version (code only)](mar-pull) tutorial, go to the location(s) where you did the pull operation(s) and modify the `.git/config` file (with vim or gedit) to update the `url` field. Indeed, in the previous tutorial, remote repositories were accessed through HTTP. Now, you can (and should) access them through SSH. It simply consists of replacing the ``https://`` prefix by ``git@`` and the forward slash in ``uliege.be/especes`` by a colon (``uliege.be:especes``). E.g., for the [ESPECES/MAR/stable](https://gitlab.uliege.be/especes/mar/stable) repository, you should have the following lines in your `.git/config`.