User Tools

Site Tools


developers:git:specificities_git_abinit

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
developers:git:specificities_git_abinit [2023/05/02 16:38] – [What is an "on-track" branch ?] Xavier Gonzedevelopers:git:specificities_git_abinit [2024/04/09 16:58] (current) – [How to synchronize with the "trunk" virtual user ?] Xavier Gonze
Line 30: Line 30:
 \\ \\
 After some modifications, using the git commands (e.g. git add, git commit ...), you can push on the gitlab server thanks to : \\ After some modifications, using the git commands (e.g. git add, git commit ...), you can push on the gitlab server thanks to : \\
-<color blue>git push </color>\\ 
-[ or\\ 
 <color blue>git push --tags  </color>     <color red>( double-dash before tags )</color>\\ <color blue>git push --tags  </color>     <color red>( double-dash before tags )</color>\\
-if tags have been introduced...]\\+\\
 In order for the modifications to be merged in the trunk, a merge request has to be issued, as described later.\\ In order for the modifications to be merged in the trunk, a merge request has to be issued, as described later.\\
 \\ \\
Line 117: Line 115:
 Then, in order to synchronize, in a first step, issue : Then, in order to synchronize, in a first step, issue :
  
-   git fetch trunk+   git fetch --tags trunk
  
 then, if the develop branch is to be updated, supposing it is checked out, merge the trunk/develop in your develop :  then, if the develop branch is to be updated, supposing it is checked out, merge the trunk/develop in your develop : 
Line 123: Line 121:
    git merge remotes/trunk/develop    git merge remotes/trunk/develop
  
-You can combine the last two commands in one as: 
- 
-   git pull trunk develop 
  
 ===== How to set up a "hotfix" branch to be merged in trunk/release-x.y ? ===== ===== How to set up a "hotfix" branch to be merged in trunk/release-x.y ? =====
Line 134: Line 129:
    git checkout release-9.8    git checkout release-9.8
    git merge remotes/trunk/release-9.8    git merge remotes/trunk/release-9.8
-   git push -u origin release-9.8+   git push -u origin release-9.8 --tags
  
 That's it ! You can now make modifications in your release-9.8, then issue a merge request to the trunk/release-9.8 . That's it ! You can now make modifications in your release-9.8, then issue a merge request to the trunk/release-9.8 .
developers/git/specificities_git_abinit.1683038336.txt.gz · Last modified: 2023/05/02 16:38 by Xavier Gonze