Connect once
Rimbra connects to GitHub through a GitHub App. You choose your personal account or an organization, and either every repository or only the ones Rimbra should see. Access is read-only and limited to that list, which you can change any time from your GitHub settings.
Once connected, your repositories are listed in Rimbra. Search, choose Import, and the first deploy starts.
What happens when you push
- 01
You push to the branch the project follows.
- 02
Rimbra creates a deployment with the commit message and author attached.
- 03
The build runs and streams its log, just like your first deploy.
- 04
When the new version answers, traffic moves to it. Nobody sees a half-built release.
When a push breaks the build
A failed build never replaces a working one. Your site keeps serving the last good version, and the failed deployment shows exactly where it stopped. Fix it, push again, and Rimbra picks it up.
Deploy on your terms
- Turn off Automatic deployments in project Settings to ship only when you choose Redeploy.
- Redeploy after changing environment variables so the running app picks them up.
- Cancel a queued or building deployment if you pushed something by mistake.
- Open any older deployment to see which commit it built.
Questions
Can Rimbra change my code?
No. The GitHub App has read-only access, and only to the repositories you chose.
My repository is not in the list.
Check the account or organization at the top of the list, then add the repository to the Rimbra app’s access list on GitHub and refresh.
Do pushes use build minutes?
Yes, each build counts toward your monthly build minutes. If your workspace runs out, new pushes are not built until you add minutes or your next cycle starts.