gitlab-ci-runner

I am trying to get gitlab’s CI to work properly with an external submodule. I have a submodule in ANOTHER repository, so no relative path. I do NOT want to use a SSH key solution. I want to use the CI token (CI_JOB_TOKEN). Documentation is NOT clear because what is possible, or not, has changed and there are texts all over the place with many different approaches and, yet, nothing that fits the basic criteria. It used to not be possible to pull submodules, with CI, if they had an absolute path, so people came up with various solutions. Then it became possible and there are a few solutions

I'm trying to settup a CI/CD pipelines with Gitlab Here is what I would like to do : NOTE: It's a typescript project unit tests && integration tests promote branch dev to branch integration Build docker image from branch integration deploy to integration env Here is the .gitlab-ci.yml I am using (i: stages: - test - promote - build - deploy cache: paths: - node_modules/ test: image: node stage: test before_script: - yarn script: - yarn test promote: image: node stage: promote only: - dev script: - git push origin HEAD:integration build image: node stage: build only: - integration script: -

In setting this up, my thinking was that I'd work on my repo and have it privately stored with Gitlab. I'd then create a .gitlab-ci.yml file which on every push it would trigger a push to a Google Source Repo which triggers actions to update the project's bucket. I went through the Generating Static Credentials guide which seems to link to a very antiquated page to which instructs you to create a .gitcookies file which will store your static credentials. I don't understand what it's giving me or how I can put those as a secret into Gitlab to use to trigger a push to a remote git repo. This