At the heart of collaboration using git is the ability to use public repositories as the basis for your own development, and in turn to publish your repository so others may use it. This article introduces the means to base your development on public git repositories and details the installation and configuration procedures for publishing your own repositories.
Two prior Linux Magazine articles, How To Git It and Embrace the Git Index, cover basic concepts about git and explain some of the details about the git index. This article introduces many new git concepts and techniques that can be used for collaborative development, including the use and manipulation of topic and tracking branches, cloning a remote repository, details on installing a server for git repositories using HTTP and git- native protocols, and publishing a public repository via the Web.
Topic And Tracking Branches
Normally, branches are used to identify conceptual lines of development within a repository. Since branches are very inexpensive in git and easy to create, it’s often desirable to have several small branches that each contain very well-defined concepts or small incremental, yet related changes. Such branches are termed topic branches. Often these branches are short-lived, and might be merged into either a temporary test branch or a long-lived “master” branch.
Another typical use for branches is to track the development from another repository and bring those changes into your repository. Branches used…
Please log in to view this content.
Not Yet a Member?
Register with LinuxMagazine.com and get free access to the entire archive, including:
