GNU/Linux Desktop Survival Guide by Graham Williams
Desktop Survival Project Home Preface Advocacy History Distributions Installing GNU/Linux Basic Survival Wajig Applications AI, Machine Learning, Data Science Android - GNU/Linux Devices Audio Backup Booting CD Chinese ChRoot Clock Command Line Databases DIA Directories Disks EcoSysL Emacs Email Evolution Files File Systems Firewalls Floppy Disks FreedomBox Glade GNOME Graphics, Images, Photos Hardware Initialisations on Booting Installation Examples Internet IOT Java KDE Kernels Keyboard Konqueror KVM Switch LATEX Log System Login Magellan MATE Mathematics Memory Modems Mounting Devices MS/Windows Music MySQL Nautilus Networks Nextcloud Network File System NFS NT File System Oracle Packages Partitions Passwords PDF Power Management PPP Presentations Printing Python R Remote Desktops Rsync Samba Scanning Science Screens Security Spreadsheet SSH Swap Teradata Data Warehouse Themes TV Unity USB Version Control Video Virtualization Voice over IP WebCam WordPress Web Sites Word Processing and Printing X XML Troubleshooting Index

CLICK HERE TO VISIT THE UPDATED SURVIVAL GUIDE

Git for Version Control

20190313 Git is the most widely used version control system today. Microsoft's centralised github platform hosts many and perhaps most of today's open source projects as well as supporting many product teams. As a popular and freedom caring alternative gitlab can either host your git repository for you or else you can install your own gitlab server. Another major commercial git provider is bitbucket.

The basic starting point for using git is to clone a pre-existing repository or one that you have forked. You can also create your own repository through the various git portals using your web browser. Once you have a git repository that you wish to work on you can clone the repository to create your own working copy:

$ git clone git@github.com:gjwgit/audit.git

This will create a copy of the repository on your local storage. By default this will also be known as the main branch. The main branch is duplicated locally as the working copy and remotely as the origin (shorthand for the original repository's URI).

You are now ready to make changes to the local repository. We will generally assume it is a repository that you have created, forked into your own account, or else have been granted access to as a developer. That is, you have commit access to the repository.