--- title: Deploy from GitHub description: Connect GitHub, link a repository to an app, and deploy on every push, with the result as a check on the commit. --- # Deploy from GitHub > **Available when the Kaviris GitHub App launches.** This page describes > how it works. Until then, deploy with your [coding agent](../quickstart/claude-code.md) > or the [`kaviris` command line](../quickstart/cli.md). Link a GitHub repository to an app, and every push to its branch becomes a deploy. This is also how [Lovable](../quickstart/lovable.md) 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: - In **GitHub**, you must be an **admin of the GitHub account** the app was installed on (the organisation's owner, or the personal account itself). This stops someone from connecting a GitHub account that isn't theirs. - In **Kaviris**, you must be an **owner or admin** of the organisation. A coding agent can't connect GitHub; it is a step for a person in the portal. 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. ## 2. Link a repository to an app 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: - as a **check run** on the commit in GitHub: passed, waiting for approval, or refused with what was found and how to fix it; - in the Kaviris portal, and by email. 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](../refusals/vuln_fixable.md), 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.