Git on Cloud

git on cloud runs git integration in resolve managed cloud infrastructure no satellite deployment is required when to use it use git on cloud when you want the fastest setup path you cannot deploy a satellite in your environment use docid 8gqksnfkotdqmlsy0dijg instead if repository access must stay inside your own cluster/network prerequisites repositories must be reachable from resolve cloud for github managed auth github access to install/authorize resolve for token auth provider username + token with required repo permissions setup option 1 github managed auth (recommended) open https //app0 resolve ai/integrations/git/edit create a cloud git connection select github auth complete the github authorization/install flow select repositories verify health check and repository listing option 2 token auth open https //app0 resolve ai/integrations/git/edit create a cloud git connection select token auth provide connection name username token repository https urls verify health check and repository listing connection schemas github auth example { "connection" { "authconfigs" { "githubapp" { "type" "github" } } } } token auth example { "connection" { "authconfigs" { "prodgithubtoken" { "type" "token", "tokenauthremoteurls" \[ "https //github com/org/repo a git", "https //github com/org/repo b git" ] } }, "tokenauthcredentials" { "prodgithubtoken" { "username" "your username", "token" "your token" } } } } optional fields { "connection" { "disablewrites" true, "disabledsubcommands" \["config", "remote"] } } disablewrites set to true to force read only mode for this integration blocks write/remediation tools if omitted, default behavior is computed from auth type ( github auth > writes enabled by default, token only > read only by default) disabledsubcommands blocks specific git \<subcommand> operations even when other git tools are available example \["config", "remote"] prevents running git config and git remote useful as a hardening control to restrict subcommands you don't want resolve to run in your repositories writes, prs, and tool access read only operations are always available (clone/fetch/search/read/history) write tools ( suggestchange , revertcommit ) are controlled by disablewrites if disablewrites is omitted defaults to false when a github auth config exists defaults to true for token only config pr api tools ( readpr , commentonpr , getfilefrompr ) require github auth with installation metadata applypatch is cli only and is not a cloud remote tool faq is token auth strictly read only? no token based connections can use write/remediation tools when disablewrites false and tool support is available are ssh urls supported? no use https repository urls