Connect your Git provider

Authorize GitHub, GitLab, or other providers on app.dflow.sh so Services can build from repositories.

Written By Zoro

Last updated 3 days ago

Services that build from source need a Git connection authorized for your Organisation.

On dFlow Cloud, you install the dFlow GitHub App or connect another supported provider through the Integrations area. Your repositories stay in the provider; dFlow receives the minimum access needed to clone and to react to webhooks.

This flow applies to the hosted dashboard at app.dflow.sh. Self-hosting the control plane uses the same integration ideas but different base URLs. See Self-hosting overview under Self-Hosting dFlow in the sidebar if you run dFlow yourself.

Before you start

  • You can sign in to the Git provider as an account that may install apps or create OAuth connections for the target org or user.
  • You know which repositories should deploy to which Application / Environment (see How dFlow is structured under Core Concepts in the sidebar).
  • If you still organize work in legacy Projects, read Legacy Projects vs Applications under Core Concepts in the sidebar and plan Migrate from legacy Projects to Applications under Migration and Release Notes in the sidebar so new Git-backed Services land in the right Application.

1. Open Integrations

  1. Sign in at app.dflow.sh.
  2. Go to Integrations (or Settings → Integrations, depending on the UI version).
  3. Choose your Git provider (for example GitHub, GitLab, Bitbucket, Azure DevOps, or Gitea).

2. Authorize dFlow

  1. Click Connect (or equivalent) next to the provider.
  2. Complete the provider’s flow: GitHub App install, OAuth consent, or personal access token if the product requests one.
  3. Grant access only to the repositories or organizations you intend to deploy from (narrow scopes reduce risk).

Expected outcome: The provider appears as Connected in dFlow and repository pickers show allowed repos when you create or edit a Service.

3. Use the connection in a Service

  1. Open your Application and add or edit a Service that builds from Git.
  2. Select the repository and branch (or tag) the build should track.
  3. Save and Deploy or Redeploy so the next build uses the linked source.

Deep dives live under Integrations overview under Integrations in the sidebar, GitHub integration under Integrations in the sidebar, and Git source integrations under Integrations in the sidebar.

If something fails

  • Integration troubleshooting under Integrations in the sidebar
  • Deployment issues under Troubleshooting in the sidebar
  • Troubleshooting overview under Troubleshooting in the sidebar

Related