GitHub copy

What you get

• A copy of each app's code in your own GitHub account
• Changes copied in both directions
• Pull requests and GitHub tools work as usual
• A commit status on GitHub for each change Whisk receives
• Conflicting changes kept on a branch of their own
• Optional, on every plan

How it works

A person installs Whisk's GitHub App on the business's GitHub account and links a repository in the app's settings. The repository must be empty or hold the app's own history. Linking is done by a person, not an agent, because anyone who can push to the repository can then deploy the app.

The app's Git repository on Whisk stays the source, and every deploy is built from it. Commits pushed to GitHub are brought in and checked like any push, including secret scanning, then deploy by the same branch rules. Commits made on Whisk are pushed to GitHub.

Copying starts on every push to either side, with a check every ten minutes in case a notice from GitHub is lost. If both sides change the same branch at once, Whisk's version wins. The GitHub commits are kept on a separate branch, so nothing is lost.

Example

An accounting practice links its client portal app to a repository in its own GitHub organisation. Its IT contractor reviews changes as pull requests on GitHub, and merging to main deploys the portal. The practice holds a full copy of the code in an account it controls.

For your coding agent

whisk github           # the link and each branch's state
whisk github sync      # compare with GitHub now

If an agent tries to link a repository, it gets NEEDS_HUMAN with the page where a person does it. The commands are in the CLI reference, and the app's own repository is described under Git hosting.