|
|
# What are branches?
|
|
|
[Branches](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell) are a fundamental part of git, and therefore the Forge. Branches provide an easy way of making "working copies" of artefacts that can be modified without affecting the main branch.
|
|
|
|
|
|
TC LI puts each CR and each plenary meeting in its own branch. A full list of branches can be found at the repository's [branches page](https://forge.etsi.org/rep/li/trial/-/branches).
|
|
|
|
|
|
# Conventions
|
|
|
TC LI uses the following branching convention in the Forge during the [CR process](Process/CR-process).
|
|
|
|
|
|
|Branch|Name|Description|Example|
|
|
|
|--|--|--|--|
|
|
|
|`main`|Current published deliverables|`main`|
|
|
|
|`meeting/{meeting title}`|Branch used as a baseline for CRs being considered at a given SA plenary meeting, and an intermediate merge target for CRs which are agreed.|`meeting/LI59e`|
|
|
|
|`cr/{deliverable}/{CR number}`|Branch representing a CR|`cr/102232-1/0987`|
|
|
|
|
|
|
Individual elements such as `{meeting title}`, `{deliverable`} and `{CR number}` are rendered following TCLI's [rendering conventions](Conventions/Rendering-conventions). |
|
|
\ No newline at end of file |