@@ -245,6 +245,24 @@ Again, you may perfectly set `CUSTOM_CA_CERTS` in your project:
* either locally in specific jobs,
* or for all jobs from one single template ([see below](#the-templates-base-job)).
## Production and integration branches
As explained earlier, _to be continuous_ [supports various Git workflows](./understand.md#supported-git-workflows)
with at least one **production branch** (`main` or `master` by default),
and possibly one **integration branch** (`develop` by default).
Those _eternal_ branches can be easily configured by overriding the following global variables (regular expression patterns):
```yaml
variables:
# default production ref name (regex pattern)
PROD_REF:'/^(master|main)$/'
# default integration ref name (regex pattern)
INTEG_REF:'/^develop$/'
```
Those variables are used internally thoughout all _to be continuous_ templates.
## Merge Request workflow
One thing that has to be chosen with GitLab CI/CD is the [Merge Request workflow strategy](https://docs.gitlab.com/ee/ci/yaml/workflow.html#switch-between-branch-pipelines-and-merge-request-pipelines).
