Branch
A named development line that Git tracks through a movable reference to a commit.
Prepare changes on a separate line
A branch is a development line. Git represents it as a named, movable reference to a commit. New commits on that line move the reference forward. Other branches need not change as a result.
In a fictional example, a date display is adjusted on fix/report-date and recorded there as a commit. The main line initially stays at its previous state. After review, the change can be integrated into the intended target line. The project workflow determines whether a pull request is required. A branch is neither a separate test server nor automatically an access barrier. Test environments, access rules and approval processes need appropriate separate arrangements.
Sources
Related terms
- GitA distributed version control system with local repositories and recorded change history.
- CommitA recorded project state with metadata and, where applicable, links to earlier states in Git.
- Pull requestA proposal to integrate changes into a target branch, with context for shared review and discussion.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps