Git integration

Cloudflare supports connecting your Cloudflare Artifacts, GitHub, GitLab, or Cursor Origin (Cursor's Git hosting platform) repository to your Cloudflare Worker, and will automatically deploy your code every time you push a change.

Adding a Git integration also lets you monitor build statuses directly in your Git provider. GitHub and Cursor Origin use pull request comments and check runs, while GitLab uses commit statuses, so you can manage deployments without leaving your workflow.

Cloudflare supports connecting Cloudflare Workers to your Artifacts, GitHub, GitLab, and Cursor Origin repositories. Workers Builds does not currently support connecting self-hosted instances of GitHub or GitLab.

If you are using a different Git provider (e.g. Bitbucket), you can use an external CI/CD provider (e.g. GitHub Actions) and deploy using Wrangler CLI.

Workers Builds provides direct integration with Artifacts repositories, GitHub and GitLab accounts that are not self-hosted, and Cursor Origin user and team repositories.

To connect an Artifacts repository, refer to the Cloudflare Artifacts integration.

When connecting a GitHub or GitLab repository for the first time, follow the prompts in the Cloudflare dashboard to authorize the Git provider. To connect Cursor Origin, install the Cloudflare app in Cursor ↗︎ and follow the installation prompts.

You can check the following pages to see if your Git integration has been installed:

• GitHub Applications page ↗︎ (if you are in an organization, select Switch settings context to access your GitHub organization settings)
• GitLab Authorized Applications page ↗︎
• Cursor codebase settings ↗︎

For details on managing provider access, refer to the GitHub, GitLab, and Cursor Origin integration guides.

To manage your Git installation:

This can be useful for managing repository access or troubleshooting installation issues by reinstalling. For more details on how to manage your installation, refer to the GitHub, GitLab, and Cursor Origin guides.