The branching conventions for the TC LI Forge Repository are summarised as follows:
||Branch representing agreement of a meeting||
||Branch representing a CR||
Meeting branches are created to represent the agreement of a meeting. The meeting branch is created by a Maintainer prior to a meeting, and serves as the source branch for CR branches for that meeting.
Post-meeting, CR branches are merged back in to the meeting branch. Once the maintainers and rappoertuers have checked the meeting branch for consistency and correctness, it is then merged back in to the master branch as the specifications are published.
CR branches are created to represent the formal-language part of a CR.
CR branches should be branched from the meeting branch where they the CR is being considered (as described in the CR making process).