This page describes Git repository connections in Developer Connect. Platform administrators can use this information to learn key concepts and decide when to use this type of connection.
Introduction
A Git repository connection is type of Developer Connect system connection that lets you create and maintain narrowly scoped connections to Git-based repositories on source code management systems outside of Google Cloud.
Use Git repository connections in situations where the user who created the connection doesn't need to be present when that connection is invoked. For example, when a Git repository is connected to your Cloud Build configuration, triggering a build upon a commit to the repository doesn't require you do anything at build time. You just grant your service account permission to use the connection, and the trigger runs upon commit.
With Git repository connections, you can configure bot services in accounts on those SCMs to handle routine tasks like cloning and indexing repositories.
For example, a Gemini Code Assist code customization user can set up a Git repository connection to a GitHub repository so that Gemini Code Assist can clone and index the connected repositories.
When you have a Git repository connection, you can create links for specific repositories. When you create a link, webhooks are enabled for the linked repository. You can also enable or disable Git proxy for a linked repository. Proxy is enabled by default when you create a connection using Google Cloud console.
Use cases
The following table lists the products and use cases that Developer Connect supports, then the SCMs that you can integrate for each use case. The table also includes links to how-to guides showing you the steps to get started with each SCM.
| Product | Use case |
|---|