Git and code
Connect GitHub, GitLab or Bitbucket with your own sign-in or a token, share an organisation git account, and deploy on every push.
REM CloudHub builds from your git repositories. It always clones as the person who asked, never with someone else's account.
Your own git sign-in
Open the Git panel (Connect git on Home, or Connectors > git sign-in).
Sign in with GitHub, GitLab or Bitbucket (OAuth). The connection shows under Your connections with Disconnect and Delete.
Personal tokens: for hosts where you prefer a token. Pick the Host (for GitLab also the GitLab server, empty for gitlab.com; GitHub is github.com only), for Bitbucket your Bitbucket username (not your e-mail), paste the Token and Save token. Read access to repositories is enough. The token is checked with the host before it is saved and is kept in the Vault.
When REM CloudHub clones, it tries your own sign-in first, then your own token, then the organisation's account.
The organisation's git account
An Owner can add one account the whole organisation uses (Connectors > Organisation git account > Add organisation account). People still clone with their own sign-in first; the organisation account is the fallback. This needs the code-host add-on in your plan.
Deploy on every push
On a project or job: Settings > Automation > Auto-update, choose Push, and copy the Webhook address and Webhook token into your repository's webhook settings at your git host. Send the token in the X-QCH-Webhook-Token header. A push to the project's branch starts a new deploy; pushes to other branches are answered "Ignored: push was not to branch". Poll checks the branch on a timer instead, for hosts that cannot send webhooks.
Protected repositories and the git proxy
Platforms can route git traffic through REM CloudHub's git proxy, which applies rules (for example protected branches) and scans pushes for secrets before they reach the host. If a push is refused, the message names the rule.
Vibe Coder
Connectors > Vibe Coder sets up your organisation's own REM Vibe Coder: where code goes (git account, repository or name pattern, default branch, pull request target and reviewers), and the organisation's Vibe Coder token (Create token, Rotate, Revoke; shown once). Owners do this themselves.