4.2.4 Sharing a Git Repository with GitLab

There are many ways to share a Git repository. The method used here is to setup a bare Git repository in a free hosting service which allows private repositories. One such provider is GitLab.

1.  Create a new private repository in GitLab. Do not import from anywhere – leave the repository empty.

2.  Once you've created the repository it will display a choice between SSH and HTTPS.
Choose HTTPS ─ it Is simpler to setup although you will need to enter the user id and password every time you connect to the remote server. Make a note of this. For example: https://git@gitlab.com/lansa/vl-ide-demo.git

     It also provides Command line instructions to be actioned in your Visual LANSA IDE Cloud instance. Follow the commands headed Git Global Setup and Existing folder or Git repository, as in this example:

Git global setup
 
git config --global user.name "lansa"
git config --global user.email "lansa@glansa.com.au"
 
Existing folder or Git repository
 
cd C:\PROGRA~2\LANSA\LANSA\LANSA\LANSA\VersionControl
git init
git remote add origin https://git@gitlab.com/lansa/vl-ide-demo.git
git add .
git commit
git push -u origin master
 

3.  Once you have pushed your LANSA Repository to GitLab, it is ready to be accessed by other users.

4..  Add Members to your project.
Members are the LANSA developers who will need to commit changes into this GitLab project. Each of these will need to create an account on GitLab for themselves first, or use an existing account. Then they may be added as a Member to the GitLab project.

     You will also need to change the project settings for each branch to unprotect it, to allow each Member (LANSA developer) to access it.

     There are other models you may use, such as having your users fork the GitLab project and then they need to send a Merge Request to have their changes accepted into the main GitLab project.