Branching model and Code Pipeline life cycle
Code residing in the main branch / at the MAIN level is ready to be released to production. There is a PROD level in the Code Pipeline life cycle, which represents production, and does not have a matching Git branch. Instead Code Pipeline promote, release and deploy are used to move code from the MAIN level into production.
Likewise, there are no Git branches directly matching the lowest levels (UT<n>, BUG1) in the Code Pipelinelife cycle. Instead, these levels get synchronized from the local developer's workspace using the Git/Code Pipeline within Total Test. The target level for any "local" activity (load, generate, build) is determined during the initial connection of the project to Code Pipeline and can by modified via the project's Code Pipeline properties.