When adding an application, if you’re using a private Git repository, you must select a Git provider and repository from your account. In addition to GitHub, you can also choose from Bitbucket or GitLab. With GitHub, you can also integrate the Sevalla GitHub Action into your workflow to seamlessly promote and deploy your applications and static sites. If you have a repository at another Git provider, you can import that repository into GitHub so you can connect it to your application hosted at Sevalla.
For security, your Git account creation date must be more than 30 days. If it is less than 30 days and you want to connect the Git account to Sevalla, please contact Sevalla’s Support Team.

​
Authenticate and authorize

The first time you add an application in Sevalla, you’ll need to connect to a Git provider so that Sevalla can access your application’s repository. When you click Add application, you must choose your Git provider and connect Sevalla to your account.
You can only connect one GitHub account to each Sevalla user. If you want to connect a different GitHub account, you must remove Sevalla access to GitHub and reconnect to the other GitHub account.

Connect Sevalla with your GitHub account.

If you aren’t currently logged in to GitHub, you’ll need to log in. On the next page, you’ll need to authenticate so you can authorize access. The last step is to authorize the Kinsta GitHub application for access to your GitHub account.
There may be occasions where you need to re-authenticate your GitHub account, for example, when we release an update to the GitHub integration or if the token has expired. You can view the expiration date for the token in your User settings (click on your username and go to User settings > Access). When the token expires, you can continue to deploy existing applications, but if you add a new one, you’ll need to connect your GitHub account again to generate a new access token.

Authorize Kinsta to connect to your GitHub account.

Go back to Sevalla, where you can begin adding your application and installing the Kinsta GitHub application to your repository.

​
Edit GitHub permissions

In the Add application modal/pop-up, click the GitHub repository field and select Edit GitHub permissions in the dropdown.

Edit GitHub permissions when adding an application.

This initiates the installation of the Kinsta GitHub application to your GitHub Account. If you have access to multiple accounts, choose the correct account to install it on.
If you do not have the correct access level, you may need to request authorization from an account owner or application manager to access the GitHub repo. For more information, see GitHub Roles in an Organization.

Install the Kinsta GitHub application to your GitHub Account.

You may notice that the authorization process is facilitated by Kinsta. Don’t worry, as Sevalla is a Kinsta product, this is a normal part of the Sevalla experience. You’ll still be interacting with Sevalla’s features and services. Just follow the prompts to complete the authorization, and you’ll be all set!
You can specify exactly what this application has access to on the next screen. We aim to have as little access as possible to your data, so we recommend not giving the application access to all repositories. Click Only select repositories, and choose the repository you would like to deploy.

Select the GitHub repository you want to deploy on Sevalla.

Finally, click Save, and you’re good to go. When you go back to Sevalla and click the GitHub repository field, you should see the authorized repository now available.

Select the repository to deploy.

​
Sevalla GitHub Action

You can seamlessly integrate Sevalla deployments into your GitHub workflows using the official Sevalla GitHub Action. With this integration, you can:
  • Trigger a deployment for any Sevalla app using an API token or deploy hook.
  • Promote deployments between Sevalla environments (e.g., staging to production).
  • Deploy static sites directly from your workflow.
  • Optionally, wait for the deployment to complete before continuing the workflow.
  • Access the deployment or promotion ID as an output variable for use in subsequent steps.
This makes it easy to automate your CI/CD pipeline and streamline your release process directly from GitHub.

​
Remove Sevalla access to GitHub

You can remove Sevalla’s access to your GitHub account either through Sevalla or GitHub.

​
Remove access via Sevalla

In Sevalla, click on your username and go to User settings > Access. In Application access, click Revoke for the GitHub application.

The GitHub application in Sevalla application access.

​
Remove access via GitHub

In GitHub, click on your user avatar and go to Settings > Applications > Authorized GitHub Apps. Click Revoke for the Kinsta GitHub application.

Kinsta GitHub application in Authorized GitHub Apps.

In the confirmation modal/pop-up, click I understand, revoke access.

Revoke access for the Kinsta GitHub application.

If you try to add a new application in Sevalla, you must authenticate and authorize the Kinsta GitHub application to reconnect it to your GitHub account.

​
Import a repository to GitHub

This guide assumes you already have a GitHub account. If not, visit their signup page to get started.
  1. In GitHub, click the plus sign (+) in the upper right corner and select Import a repository.
  2. Copy the repository URL from your other Git provider and paste it into Your old repository’s clone URL in GitHub.
  3. If you are a member of an Organization in GitHub, choose an Owner for your new repository.
  4. Enter your Repository name.
  5. Choose a privacy setting for the new repository and click Begin import.

Import repository to GitHub.

  1. If the repository at the other Git provider is private, enter your Username/Login and Password when prompted and click Submit.
If you enabled SAML SSO or 2FA on your account at the other Git provider, enter a personal access token with read permission for the repository in the Password field instead of your password.

​
Troubleshooting

​
Missing repositories

If you’re having trouble seeing your repositories in the Add application modal/pop-up, you may need to re-authenticate and authorize the Kinsta GitHub application. To do that, start by removing access between Sevalla and GitHub as described above. In Sevalla, in the Add application modal/pop-up (Add service > Add application), go through the authenticate and authorize steps to connect Sevalla to your GitHub account again.

​
Conflicting namespaces

The Conflicting namespaces error appears when a Git account is connected to another Sevalla user account. Your Git account can only be linked to one Sevalla account; if you have multiple Sevalla accounts, you must use multiple Git accounts. To resolve this error, you must log in to your other Sevalla account and remove Sevalla access to GitHub.