Skip to content

Git Providers

Git Providers — sometimes known as software forges or Source Code Managers (SCMs) — provide a set of tools to host and collaborate on codebases using Git.

Daytona allows you to integrate your preferred Git Provider, enhancing your development workflow. This integration enables you to access and manage your repositories directly within Daytona, simplifying workspace creation from existing projects.

By adding a Git Provider, your credentials are securely embedded into your Workspaces. This allows for seamless Git operations without repeated authentication.

Add a Git Provider

  1. Run the following command to add a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to select the Git Provider you want to add.

Choose a Git provider
GitHub
GitLab
Bitbucket
Other
  1. Select the Git Provider you want to configure from the list:

  • GitHub

    Select if you are hosting repositories on GitHub.

  • GitLab

    Select if you are hosting repositories on GitLab.

  • Bitbucket

    Select if you are hosting repositories on Atlassian’s Bitbucket Cloud platform.

  • GitHub Enterprise Server

    Select if you are hosting repositories on GitHub Enterprise Server.

  • GitLab Self-Managed

    Select if you are hosting repositories on GitLab’s self-hosted platform.

    Self-hosted GitLab Community Edition (CE) installations, GitLab Self-Managed, and GitLab Dedicated platforms are supported.

  • Bitbucket Server

    Select if you are hosting repositories on Bitbucket Server.

  • Codeberg

    Select if you are hosting repositories on Codeberg.

  • Gitea

    Select if you are hosting repositories on Gitea.

  • Gitness

    Select if you are hosting repositories on Gitness.

  • Azure DevOps

    Select if you are hosting repositories on Azure DevOps.

  • AWS CodeCommit

    Select if you are hosting repositories on AWS CodeCommit.

  • Gogs

    Select if you are hosting repositories on Gogs.

  • Gitee

    Select if you are hosting repositories on Gitee.

  1. Enter your Git Provider credentials for Daytona to authenticate and enable secure access to your repositories.
Personal access token
>

Some Git Providers require additional information such as your username or the URL of your self-managed API instance to complete the configuration.

  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

List Connected Git Providers

Daytona allows you to keep track of your Git Providers by listing all previously created Git Providers.

  1. Run the following command to list currently connected Git Providers:
Terminal window
daytona git-providers list

Upon running this command, Daytona will display a list of your connected Git Providers.

GitHub (alias)
GitLab (alias)

Update a Git Provider

Daytona allows you to update an existing Git Provider, enabling you to apply the latest enhancements and bug fixes.

  1. Run the following command to update a Git Provider:
Terminal window
daytona git-providers update

Upon running this command, Daytona will display a list of your connected Git Providers.

Choose a Git provider
> github (alias)

  1. Select the Git Provider you want to update from the list.

  2. Enter your Git Provider credentials for Daytona to authenticate and enable secure access to your repositories.

Personal access token
>

Some Git Providers require additional information such as your username or the URL of your self-managed API instance to complete the configuration.

  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful update, Daytona will display the following message:

Git provider has been updated

Delete a Git Provider

Daytona allows you to delete Git Providers, helping you manage and delete those that are no longer needed. Once a Git Provider is deleted, you will not be able to manage or deploy Workspaces without adding another Git Provider.

  1. Run the following command to delete a Git Provider:
Terminal window
daytona git-providers delete

Upon running this command, Daytona will display a list of existing Git Providers you can delete.

Choose a Git provider
GitHub
GitLab
  1. Select the Git Provider you want to delete.

Upon successful selection, Daytona will display the following message:

Git provider has been removed

GitHub

Daytona allows you to connect your GitHub account and access your repositories directly from Daytona.

  1. Run the following command to add GitHub as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select GitHub from the list.

Choose a Git provider
> GitHub

After selecting GitHub as your Git Provider, you will be prompted to enter a Personal Access Token.

For more information on creating a Personal Access Token, visit GitHub’s Creating a personal access token (classic) documentation.

  1. Enter your Personal Access Token for Daytona to authenticate and enable secure access to your GitHub repositories.
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

GitLab

Daytona allows you to connect your GitLab account and access your repositories directly from Daytona.

  1. Run the following command to add GitLab as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select GitLab from the list.

Choose a Git provider
> GitLab

After selecting GitLab as your Git Provider, you will be prompted to enter a Personal Access Token.

For more information on creating a Personal Access Token, visit GitLab’s Create a personal access token documentation.

  1. Enter your Personal Access Token for Daytona to authenticate and enable secure access to your GitLab repositories.
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

Bitbucket

Daytona allows you to connect your Bitbucket account and access your repositories directly from Daytona.

  1. Run the following command to add Bitbucket as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Bitbucket from the list.

Choose a Git provider
> Bitbucket

After selecting Bitbucket as your Git Provider, you will be prompted to enter a Username (your Atlassian username) and a Personal Access Token (App Password).

For more information on creating a Personal Access Token, visit Bitbucket’s Create an App password documentation.

  1. Enter your Username and Personal Access Token for Daytona to authenticate and enable secure access to your Bitbucket repositories.
Username
>
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

GitHub Enterprise Server

Daytona allows you to connect your GitHub Enterprise Server account and access your repositories directly from Daytona.

  1. Run the following command to add GitHub Enterprise Server as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select GitHub Enterprise Server.

Choose a Git provider
> Other
Choose a Git provider
> GitHub Enterprise Server

After selecting GitHub Enterprise Server as your Git Provider, you will be prompted to enter a Self-Managed API URL (the base URL for your GitHub Enterprise Server instance’s API) and a Personal Access Token.

For more information on creating a Personal Access Token, visit GitHub’s Creating a personal access token (classic) documentation.

  1. Enter your Self-Managed API URL and Personal Access Token for Daytona to authenticate and enable secure access to your Github Enterprise repositories.
Self-managed API URL
For example: https://github-host
>
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

GitLab Self-Managed

Daytona allows you to connect your GitLab Self-Managed account and access your repositories directly from Daytona.

  1. Run the following command to add GitLab Self-Managed as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select GitLab Self-managed.

Choose a Git provider
> Other
Choose a Git provider
> GitLab Self-managed

After selecting GitLab Self-Managed as your Git Provider, you will be prompted to enter a Self-Managed API URL (the base URL for the self-hosted GitLab API) and a Personal Access Token.

For more information on creating a Personal Access Token, visit GitLab’s Create a personal access token documentation.

  1. Enter your Self-Managed API URL and Personal Access Token for Daytona to authenticate and enable secure access to your GitLab Self-Managed repositories.
Self-managed API URL
For example: http://gitlab-host/api/v4/
>
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

Bitbucket Server

Daytona allows you to connect your Bitbucket Server account and access your repositories directly from Daytona.

  1. Run the following command to add Bitbucket Server as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select Bitbucket Server.

Choose a Git provider
> Other
Choose a Git provider
> Bitbucket Server

After selecting Bitbucket Server as your Git Provider, you will be prompted to enter a Username (your Atlassian username), Self-managed API URL (the base URL for your Bitbucket Server instance’s API), and a Personal Access Token (App Password).

For more information on creating a Personal Access Token, visit Bitbucket’s Create an App password documentation.

  1. Enter your Username, Self-managed API URL, and Personal Access Token for Daytona to authenticate and enable secure access to your Bitbucket Server repositories.
Username
>
Self-managed API URL
For example: https://bitbucket.host.com/rest
>
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

Codeberg

Daytona allows you to connect your Codeberg account and access your repositories directly from Daytona.

  1. Run the following command to add Codeberg as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select Codeberg.

Choose a Git provider
> Other
Choose a Git provider
> Codeberg

After selecting Codeberg as your Git Provider, you will be prompted to enter a Personal Access Token.

For more information on creating a Personal Access Token, visit Codeberg’s Generating an Access Token documentation.

  1. Enter your Personal Access Token for Daytona to authenticate and enable secure access to your Codeberg repositories.
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

Gitea

Daytona allows you to connect your Gitea account and access your repositories directly from Daytona.

  1. Run the following command to add Gitea as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select Gitea.

Choose a Git provider
> Other
Choose a Git provider
> Gitea

After selecting Gitea as your Git Provider, you will be prompted to enter a Self-Managed API URL (the base URL for the Gitea installation’s API) and a Personal Access Token.

For more information on creating a Personal Access Token, visit Gitea’s Generating and listing API tokens documentation.

  1. Enter your Self-Managed API URL and Personal Access Token for Daytona to authenticate and enable secure access to your Gitea repositories.
Self-managed API URL
For example: http://gitea-host
>
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

Gitness

Daytona allows you to connect your Gitness account and access your repositories directly from Daytona.

  1. Run the following command to add Gitness as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select Gitness.

Choose a Git provider
> Other
Choose a Git provider
> Gitness

After selecting Gitness as your Git Provider, you will be prompted to enter a Self-Managed API URL (the base URL for the Gitness installation’s API) and a Personal Access Token.

For more information on creating a Personal Access Token, visit Gitness’ Generate user token documentation.

  1. Enter your Self-Managed API URL and Personal Access Token for Daytona to authenticate and enable secure access to your Gitness repositories.
Self-managed API URL
For example: http://gitness-host/api/v1/
>
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

Azure DevOps

Daytona allows you to connect your Azure DevOps account and access your repositories directly from Daytona.

  1. Run the following command to add Azure DevOps as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select Azure DevOps.

Choose a Git provider
> Other
Choose a Git provider
> Azure DevOps

After selecting Azure DevOps as your Git Provider, you will be prompted to enter a Self-Managed API URL (the base URL for the Azure DevOps installation’s API) and a Personal Access Token.

For more information on creating a Personal Access Token, visit Azure DevOps’ Create a Personal Access Token documentation.

  1. Enter your Self-Managed API URL and Personal Access Token for Daytona to authenticate and enable secure access to your Azure DevOps repositories.
Self-managed API URL
For example: https://dev.azure.com/organization
>
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

AWS CodeCommit

Daytona allows you to connect your AWS CodeCommit account and access your repositories directly from Daytona.

  1. Run the following command to add AWS CodeCommit as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select AWS CodeCommit.

Choose a Git provider
> Other
Choose a Git provider
> AWS CodeCommit

After selecting AWS CodeCommit as your Git Provider, you will be prompted to enter a Username, a Self-Managed API URL (the base URL for the AWS CodeCommit installation’s API) and a Personal Access Token.

For more information on creating a Personal Access Token, visit AWS CodeCommit’s Authentication and access control documentation.


  1. Enter your Username, Self-Managed API URL, and Personal Access Token for Daytona to authenticate and enable secure access to your AWS CodeCommit repositories.
Username
>
Self-managed API URL
For example: https://ap-south-1.console.aws.amazon.com
>
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

Gogs

Daytona allows you to connect your Gogs account and access your repositories directly from Daytona.

  1. Run the following command to add Gogs as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select Gogs.

Choose a Git provider
> Other
Choose a Git provider
> Gogs

After selecting Gogs as your Git Provider, you will be prompted to enter a Self-Managed API URL (the base URL for the Gogs installation’s API) and a Personal Access Token.

To create a Personal Access Token follow these steps:

  1. Log into Gogs, and click your profile avatar to open the user menu.
  2. Click Your Settings in the user menu. Make sure you have admin access to the repository.
  3. Navigate to Applications in the sidebar.
  4. In the Manage personal access tokens section, click Generate New Token.
  5. Type a name for your token and click Generate Token.
  6. Copy and save the token securely (it won’t be shown again).

  1. Enter your Self-Managed API URL and Personal Access Token for Daytona to authenticate and enable secure access to your Gogs repositories.
Self-managed API URL
For example: https://gogs-host.com
>
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered

Gitee

Daytona allows you to connect your Gitee account and access your repositories directly from Daytona.

  1. Run the following command to add Gitee as a Git Provider:
Terminal window
daytona git-providers add

Upon running this command, Daytona will prompt you to choose a Git Provider you want to add. Select Other from the list, and then select Gitee.

Choose a Git provider
> Other
Choose a Git provider
> Gitee
  1. Enter your Personal Access Token for Daytona to authenticate and enable secure access to your Gitee repositories.

To create a Personal Access Token follow these steps:

  1. Log into Gitee, and click your profile avatar to open the user menu.
  2. Click Settings in the user menu. Make sure you have admin access to the repository.
  3. Navigate to Personal access tokens in the sidebar.
  4. In the Manage personal access tokens section, click Generate New Token.
  5. Enter a description for your token, and select following scopes:
    • user_info
    • projects
    • pull_requests
    • groups
    • emails
  6. Click Commit to generate the token. You’ll prompted to enter your password for verification.
  7. Copy and save the token securely (it won’t be shown again).
Personal access token
>
  1. Enter your Git Provider alias to identify it within Daytona.
Alias
Will default to username if left empty
>

Upon successful authentication, Daytona will display the following message:

Git provider has been registered