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 Branch Naming

A common convention for naming branches is to begin with a token, then a slash, then descriptive name. This can be problematic as when URIs are created to the branch whereby the slash is ambiguous. Nonetheless, the use of slash is common and supported by some tools.

Common tokens include feat (feature), wip (work in progess), bug, new, test, dev, doc.

For a team the token may be the user's name, like kayon/addcolour. In general this is discouraged as it can lead to a hesitation of others to contribute to that branch as it appears to be owned by Kayon. If that is the intention then that is fine. Otherwise avoid this apparent ownership becoming a blocker to others contributing.