Git

use the git integration to connect resolve ai to your codebase — to query code during investigations, pull relevant evidence, and propose code changes for you to review resolve's git integration is designed to fit how your organization is set up it supports both a cloud only and a hybrid (satellite based) architecture, and multiple authentication methods, so a single integration can cover github com, github enterprise (cloud or server), gitlab, bitbucket, azure devops, and self hosted git how resolve connects to your codebase through git connecting resolve ai to your code comes down to two independent choices where git commands run git on cloud (resolve managed) or git on satellite (your kubernetes / ecs) how resolve authenticates github (resolve ai's app for github), ghe (bring your own github app), or token (pat) all three work on both cloud and satellite 1\ choosing an execution plane cloud or satellite your first decision is where resolve actually clones, fetches, and queries your repositories the right choice depends on your network reachability, your data residency requirements, and how much infrastructure your team is prepared to operate area git on cloud git on satellite where git commands run resolve managed cloud infrastructure a satellite worker you deploy in your environment who operates infrastructure resolve your team repository reachability reachable from resolve cloud reachable from your satellite, including private networks and air gapped instances storage location resolve managed persistent storage a volume on your satellite (pvc for kubernetes, efs for ecs) the resolve satellite is supported on kubernetes and on aws ecs fargate the kubernetes deployment stores repositories on a gitvolume (pvc is recommended for production); the ecs deployment uses an efs volume both are functionally identical, so the choice comes down to whichever infrastructure your team already operates once you've decided, follow the matching setup guide set up git on cloud docid\ jnylm3jccqrvieuavzdqs for resolve managed execution set up git on satellite (kubernetes) docid\ xpgmd3gralx1wkgfybh8a for in cluster execution set up satellite on ecs docid 8i ecgujrxynd72r3aiyk for aws fargate execution 2\ choosing an authentication method after picking an execution plane, decide how resolve proves identity to your git host all three auth types work on both cloud and satellite — the choice is driven by which git host your code lives on , your security policy , and how you want to manage the git app github — connects to github com through resolve ai's app for github you complete an oauth style installation, and resolve handles token rotation automatically ghe — connects through a custom github app that you own, on any github variant (github com, github enterprise cloud, or github enterprise server) you provide the app id, installation id, and private key, and resolve calls the api base url you configure token — connects to non github providers (gitlab, bitbucket, azure devops, self hosted git) or to github via pat resolve authenticates with the username and personal access token you provide one integration can use all three auth types a single git integration can carry multiple auth configs side by side under authconfigs — for example, one github config for github com repos, one ghe config for an on prem ghe instance, and one or more token configs for gitlab or bitbucket each is keyed independently and matched to its credentials match your setup to an auth type your setup pick why standard github com, no policy on which github app you use github one click install of resolve ai's app for github — no app credentials, no private key, no base url fastest path github com, but compliance / audit / scoped permissions require a customer owned app ghe you operate the app, control the permission set, and rotate keys on your schedule works against https //api github com github enterprise cloud ( ghe com ) ghe resolve ai's app for github is github com only; ghe cloud requires your own app on your tenant github enterprise server (on prem), reachable from resolve cloud ghe on cloud your own app on your ghe server, with baseurl pointing at /api/v3 github enterprise server (on prem), only reachable from inside your network ghe on satellite code never leaves your network the satellite reaches ghe server directly gitlab, bitbucket, azure devops, self hosted git, or github via pat token app based auth doesn't apply for non github providers for github via pat, use this when an app install is impossible (locked down org, individual account repos) mixed providers (e g github com + on prem ghe + gitlab) multiple auth configs in one integration github + ghe + token can coexist under authconfigs once you've decided, follow the matching walkthrough connect via resolve ai's app for github docid\ jr5wemheelnozhvsz81ne for github auth on github com bring your own github app docid\ jr5wemheelnozhvsz81ne for ghe auth (github com, ghe cloud, or ghe server) token setup lives under option 3 in the cloud docid\ jnylm3jccqrvieuavzdqs or satellite docid\ xpgmd3gralx1wkgfybh8a guide what resolve can do once connected reads vs writes these behaviors apply to both cloud and satellite reads are always enabled cloning, fetching, searching, reading files, viewing history, generating diffs, and inspecting blame data write/remediation tools (proposing code changes, opening prs) are controlled by disablewrites with a github or ghe auth config, writes are enabled by default with token only auth, writes are disabled by default set disablewrites explicitly in your connection config to override either default for the full schema ( authconfigs , tokenauthcredentials , gheauthcredentials , disabledsubcommands , certificate overrides), see the git on cloud docid\ jnylm3jccqrvieuavzdqs or git on satellite docid\ xpgmd3gralx1wkgfybh8a setup guide get started you want… start here fastest onboarding, no infra work set up git on cloud docid\ jnylm3jccqrvieuavzdqs in cluster execution on kubernetes set up git on satellite docid\ xpgmd3gralx1wkgfybh8a aws native execution without kubernetes set up satellite on ecs docid 8i ecgujrxynd72r3aiyk resolve ai's app for github walkthrough app for github → resolve ai's app docid\ jr5wemheelnozhvsz81ne bring your own github app walkthrough app for github → byo github app docid\ jr5wemheelnozhvsz81ne