Git is an open source Version Control System (VCS).
This guide provides simple instructions for setting up Git, but there is far more to know and understand than the setup and it is beyond the scope of this guide. You must receive training on the use of Git as with any VCS.
For information, refer to the following:
4.2.1 Considerations when Installing a New VCS Master for Git in the Cloud
4.2.2 Setting up a New VCS Master for Git in the Cloud
4.2.3 Migrating a Partition from a Slave to a VCS Master for Git in the Cloud
4.2.4 Sharing a Git Repository with GitLab
4.2.5 Setting up 2nd and Subsequent Developers to use a VCS Master for Git in the Cloud
4.2.6 Release Management with a VCS Master for Git in the Cloud
4.2.7 Upgrading a VCS Master for Git in the Cloud
Tip: When you modify an object in the Development Environment it saves a copy to the VCS Working Folder and this is then picked up by the VCS as a difference.
When you import into the Repository it is not saved into the VCS Working Folder. You must explicitly save the set of objects to the working folder.
A useful tool for this is to always use the Development Environment Import which has an option to create a Repository list. You can then use that list to save all the imported objects to the VCS working Folder.
