Portal

Deploy from GitHub

Available when the Kaviris GitHub App launches. This page describes how it works. Until then, deploy with your coding agent or the kaviris command line.

Link a GitHub repository to an app, and every push to its branch becomes a deploy. This is also how Lovable apps reach Kaviris, through Lovable's GitHub sync.

1. Connect GitHub (once per organisation)

  1. In the Kaviris portal, open GitHub and choose Connect GitHub. This installs the Kaviris GitHub App on the GitHub account or organisation you pick, for the repositories you pick.
  2. GitHub sends you back to a Kaviris confirm page that says which GitHub account is being connected to which Kaviris organisation. Confirm it.

Two people's rights are checked here:

The GitHub App can read the contents of the repositories you chose and report results as checks. Nothing else: it cannot push, open pull requests or see other repositories.

Pick the repository and the branch (the default branch if you don't say), in the portal or through your agent (list_github_repos, then link_github). One repository and branch per app. Linking needs an owner or admin of the Kaviris organisation; an agent acting for a member gets an answer that points to the portal.

3. Every push is a deploy

Each push to the linked branch becomes a deploy of that commit. Kaviris fetches the code itself, so no GitHub token ever reaches your app or the build. From then on it is an ordinary deploy: built, checked, and live if all is well.

The result comes back:

If a deploy is refused, the running version stays, and the check says what to fix. If it only needs a contract change approved, approve it in the portal (or ask your agent) and the deploy continues. Recommendations, such as an upgrade for a vulnerable library, show in the check too but never fail it.

Disconnecting

Uninstall the Kaviris GitHub App in GitHub's settings, or disconnect it in the Kaviris portal. Apps that were linked keep running the version they have; pushes no longer deploy.

This page as Markdown