Translated from 日本語 • View original Good morning. This is Infra Miyashita.
Last time, we explained the installation of source tree and key registration, so this time we will explain the connection with gitlab. Since there is gitlab in the company, it is assumed that you will be connected to gitlab. (Of course, there is also a gitlab account)
In the menu of the gitlab profile screen, select SSH keys.
You can check the list of keys that have already been registered. Click Add SSH key in the upper right corner.
When you move to the key registration screen, put an easily identifiable name in the Title (it will be automatically generated if you do not enter it), paste the public key you created last time in the Key area, and register it with "Add key".
If it is displayed in the list of registration keys, the registration is complete.
Go back to the source tree again.
Now clone the gitlab repository. Start with Create New/Clone.
This time, we will be using the gitlab repository, so select the "Clone Repository" tab and enter the gitlab connection information in the original path/URL. (Example: http://192.168.0.250/infra/projectX.git) The in-house gitlab can be connected via http, but any method that can be connected with git or SSH is fine. After entering, the connection will be automatically confirmed and you can confirm the success or failure of the connection. - Specify the destination where the cloned data will be saved in the destination path. ・Keep the bookmark in the repository as it is. ・The name is the name displayed on the sourcetree, so please give it a name so that you can see which repository it is.
Once you have entered the required information, you can start with "Clone".
Depending on the amount of data, wait a while and the cloning will be completed in the destination path.
I was successfully registered. This will allow you to live git from sourcetree.
As a basic task, it looks like this until you push. When you modify the file on the PC side, it will change to a change icon, so click "Add" or click on the file.
The update file will then move to the file staged in index.
Next, select "Commit" to allow you to fill in comments, so "Commit" with comments that follow the rules.
When you commit, a red number appears at the "push" mark. This is a note that there is a fill to push, so I will push it when all the corrections are completed.
You can push it as it is, but if you are working with a large number of people, it may conflict, so you will "pull" it once.
After confirming that there is no difference with the master, "push".
If you look at the gitlab dashboard, you will see that it has been pushed.
If you check the contents in detail, you can check the changes such as differences.
This is the basic operation, and there is still a lot to learn to actually operate such as cutting branches, merging, and checking out. Let's implement it in accordance with the administrator's policy. (Explanation of how to operate another time)
Thank you very much.