@@ -25,12 +25,14 @@ working in your self-managed server:
1. Use the right GitLab Synchronization option(s) when [running the GitLab Copy CLI](./basic.md#run-the-gitlab-copy-cli) for first the time:
*`--dest-sync-path` to override the GitLab destination root group path,
*`--max-visibility` to override the maximum visibility of projects in the destination group.
*`--max-visibility` to override the maximum visibility of projects in the destination group,
*`--alt-ci=.gitlab-ci-namespaced.yml` to preferentially use the CI/CD configuration file `.gitlab-ci-namespaced.yml` in your locally copied projects, when it is present.
For more info about GitLab Copy CLI options, please [refer to the doc](https://gitlab.com/to-be-continuous/tools/gitlab-cp#usage).
2. Set the right variable(s) in your local copy of the [tools/gitlab-sync](https://gitlab.com/to-be-continuous/tools/gitlab-sync) project
when [configuring the TBC synchronization](./basic.md#sync-your-local-copy-of-tbc) for first time:
*`$DEST_SYNC_PATH` to override the GitLab destination root group path,
*`$MAX_VISIBILITY` to override the maximum visibility of projects in the destination group.
*`$MAX_VISIBILITY` to override the maximum visibility of projects in the destination group,
*`$ALT_CI` (set to `.gitlab-ci-namespaced.yml`) to preferentially use the CI/CD configuration file `.gitlab-ci-namespaced.yml` in your locally copied projects, when it is present.
3. Set the right variable(s) in your local copy of the
