Secrets and source control

Sync your app's code with GitHub

Keep your app's code in a private GitHub repository that Ahamo keeps in sync both ways, with conflicts you settle yourself.

On this page

Ahamo can create a private GitHub repository for your app and keep it in sync with the app's code both ways. changes made in Ahamo are pushed to GitHub, and commits made on GitHub come back into the app after Ahamo checks them. Ahamo never force-pushes and never merges on its own.

The sync uses one branch, main in a repository Ahamo created, or the repository's default branch for an app imported from a private repository. Ahamo looks at GitHub about once a minute, so a push to that branch reaches the app within a minute or two; no webhook is needed. Pushes to other branches stay on GitHub.

When to use it

  • A developer wants to work on the code in their own editor.
  • Your organisation keeps all source code in GitHub, or wants its review tools on it.

To bring an existing GitHub repository into a new app instead, import it when you create the app:

  • A private repository is imported through a GitHub connection, and the app stays connected to that same repository, because the import's branch is the synced branch, both ways.
  • A public repository can be imported without a connection. The app then only records where it came from and nothing syncs. To sync, Disconnect it in Versioning and Connect, which creates a new private repository for the app rather than connecting the public one.

If the repository uses Supabase, see If you import a repository that uses Supabase.

How to use it

  1. Open Versioning.
  2. In the GitHub card, select Connect and enter a Repository name (letters, digits, dots, dashes or underscores, up to 100 characters).
  3. Select Continue on GitHub and approve the Ahamo app for your account or organisation. Only an owner of the GitHub account or organisation can install it; anyone else sends the owner an install request, and connects again once the owner approves it.

The status then becomes Synced. From then on each saved change in Ahamo appears as a commit on GitHub, and pushes to the repository come back into the app.

A GitHub commit Ahamo can't accept (for example one that breaks the build) shows Validation failed, and the app keeps its last good code. When both sides changed, the status is Conflict and neither side moves until you choose Use Ahamo source or Use GitHub source.

Plans and limits

The same on every plan.

RuleValue
Repositories per app1 (created by Ahamo, private, or the private repository the app was imported from)
Synced branchmain, or the imported repository's default branch
Inbound commitsChecked and taken in about once a minute
Change the connectionPeople who can configure the app's integrations
See the statusEveryone who can open the app

Troubleshooting

The GitHub card always says what stopped the sync and the one thing to do about it.

Reconnect needed. GitHub no longer accepts Ahamo's access, for example after the app was uninstalled or lost a permission. Select Reconnect.

Sync paused because Ahamo's GitHub app has no access to the repository. The app's installation lists only some repositories and this one isn't among them. On GitHub, open Settings › Applications › Ahamo › Configure and add the repository under Repository access, or select Reconnect, which takes you there.

Sync paused because GitHub refused Ahamo's push. A branch protection rule or ruleset on the synced branch blocks Ahamo. On GitHub, open Settings › Branches (or Rules) and allow Ahamo's GitHub app to push to the branch, then select Retry now.

Sync paused by a temporary problem. Ahamo retries every minute by itself; reconnecting doesn't help. If it stays for more than a few minutes, report it from the Feedback button.

The install request was sent to the owner. You may not install GitHub apps on that account. Ask its owner to approve the request on GitHub, then select Connect again.

Missing repository. The repository was deleted or renamed. Select Replace repository to create a new one, or Disconnect.

"GitHub is not set up on this Ahamo installation yet." Your organisation's Ahamo doesn't have its GitHub connection yet; ask your administrator.

On this page