Deploy on every push: the GitHub integration

Published on 2 min read

Connect a GitHub repository to your app and every push to the chosen branch redeploys your code automatically, no ZIP, no CLI, no VS Code.

Until now, updating an app's code was always something you triggered: uploading a ZIP in the dashboard, running mybotcloud deploy, or using the VS Code extension. With the GitHub integration, that can now happen on its own: connect a repository and a branch, and every git push to it triggers a deploy automatically, through the same staged-progress mechanism the "Atualizar" (Update) tab already uses.

What MyBotCloud can see in your repository

The integration runs through a GitHub App owned by the platform (not a personal token of yours). When you install it, you pick exactly which repositories to allow, and the App only asks for two permissions:

  • Contents: read-only — to download the code when you push.
  • Metadata: read-only — the minimum GitHub requires for any App.

We don't read Issues, Actions, Settings, other repositories you didn't allow, or anything beyond that. You can revoke access at any time directly on GitHub (Settings → Applications → Installed GitHub Apps), with no need to tell us.

How to connect

  1. Open your application in the dashboard and go to the GitHub tab.
  2. Click Connect GitHub. You'll be taken to GitHub itself to install the App and pick which repository (or repositories) to allow.
  3. Back in the dashboard, choose the repository and branch from the list (pulled straight from the installation, no need to type owner/repo by hand).
  4. Click Save connection.

From then on, any git push to the chosen branch redeploys the code: the platform downloads the repository's latest state, packages it the same way a manually uploaded ZIP would be, and runs it through the same deploy stages (environment → code → dependencies → start → check).

What stays the same

  • Environment variables stay separate from the code. A push never carries .env files or secrets: those are still set in Manage → Environment variables, as always.
  • CLI, VS Code and MCP keep working normally alongside it. Connecting GitHub doesn't disable mybotcloud deploy; they're two ways to update the same app, and whichever ran last is what's live.
  • If an automatic deploy fails (a missing token, for example), the app keeps running the previous version, and you see the failure reason in the logs, the same as any other deploy.

Disconnecting

In the same GitHub tab, click Disconnect. That stops future pushes from triggering a deploy. If you also want to remove the platform's access to the repository (not just this app), that's done directly in GitHub's own settings.

Still stuck? Open a ticket in Support in the dashboard, or join our Discord.

  • github
  • deploy
  • tutorial
  • cli

← Back to the blog