Changes

From SME Server
Jump to navigationJump to search
Line 94: Line 94:  
=Local rpm build=
 
=Local rpm build=
 
=Saving the Source code to Gitea=
 
=Saving the Source code to Gitea=
''git status'' is very useful to see what changes have been made as compared to the version in the remote gitea/git server. The changed files are flagged in red before they have been locally staged and green afterwards.
+
''git status'' is very useful to see what changes have been made as compared to the version in the remote gitea/git server. The changed files are flagged in red before they have been locally staged and green afterwards (staged = call ''git add'').
    
''git pull'' can be used to bring any existing clone directory up to the latest on the server. However if the local version has been changed since the original clone and not pushed back and therefore deviates from the remote version then an error message is seen and the pull will fail. Unless you have good reason to retain your local changes, the easiest way is to delete the local directory and re-clone.   
 
''git pull'' can be used to bring any existing clone directory up to the latest on the server. However if the local version has been changed since the original clone and not pushed back and therefore deviates from the remote version then an error message is seen and the pull will fail. Unless you have good reason to retain your local changes, the easiest way is to delete the local directory and re-clone.   
Line 101: Line 101:     
''git commit -m "<comment>"'' This will prepare to push the changed files back to the remote repo.
 
''git commit -m "<comment>"'' This will prepare to push the changed files back to the remote repo.
 +
 +
''git push'' WILL ACTUALLY do the update to the remote repo.
    
=Tagging and starting a build=
 
=Tagging and starting a build=

Navigation menu