Changes

Page history
Update Pushing MAR code changes from a cluster or lab machine authored by Grailet Jean-François's avatar Grailet Jean-François
Hide whitespace changes
Inline Side-by-side
mar-push.md
View page @ 178ba003
...@@ -3,6 +3,7 @@ title: Pushing MAR code changes from a cluster or lab machine ...@@ -3,6 +3,7 @@ title: Pushing MAR code changes from a cluster or lab machine
--- ---
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.
>**Reminders about ``git`` terminology:** >**Reminders about ``git`` terminology:**
...@@ -50,7 +51,7 @@ git config --global user.email ‘Jean-Francois.Grailet@uliege.be’ ...@@ -50,7 +51,7 @@ git config --global user.email ‘Jean-Francois.Grailet@uliege.be’
``` ```
git config --global credential.helper “store --file ~/.uliege-gitlab-credentials” git config --global credential.helper “store --file ~/.uliege-gitlab-credentials”
``` ```
3. Using ``vim`` or ``gedit``, create the document `~/.uliege-gitlab-credentials` and write the following sequence, replacing `[login]` with your GitLab username and `[token]` with the token created in the [previous section](mar-push). Save and exit the editor. 3. Using ``vim`` or ``gedit``, create the document `~/.uliege-gitlab-credentials` and write the following sequence, replacing `[login]` with your GitLab username and `[token]` with the token created in the [previous section](mar-push#step-1-create-an-access-token-on-gitlab-only-once). Save and exit the editor.
``` ```
https://[login]:[token]@gitlab.uliege.be https://[login]:[token]@gitlab.uliege.be
``` ```
...@@ -90,4 +91,6 @@ git push origin main ...@@ -90,4 +91,6 @@ git push origin main
* ``git log`` alone will print a detailed history. * ``git log`` alone will print a detailed history.
* ``git log --oneline`` prints a summarized history, with one line per commit. * ``git log --oneline`` prints a summarized history, with one line per commit.
* ``git log -X`` prints only the X last commits. E.g., ``git log -10`` will give the last 10 commits. It can also work in conjunction with ``--oneline``, e.g., ``git log -10 --oneline`` will print the last 10 commits with one line per commit. * ``git log -X`` prints only the X last commits. E.g., ``git log -10`` will give the last 10 commits. It can also work in conjunction with ``--oneline``, e.g., ``git log -10 --oneline`` will print the last 10 commits with one line per commit.
* Alternatively, ``git show`` will print a detailed description, complete with all changes, of the latest commit. * Alternatively, ``git show`` will print a detailed description, complete with all changes, of the latest commit.
\ No newline at end of file
_Parts of this tutorial have been translated from French notes with [DeepL](https://www.deepl.com)._
\ No newline at end of file