Git hosting

What you get

• A private Git repository for every app
• Push to main to deploy production
• Other branches stored without deploying
• Secret scanning on every push
• whisk.yaml checked before a push is accepted
• Full history, ready to clone anywhere

How it works

Every app's code lives in a plain Git repository on Whisk, reached over HTTPS. A push to the main branch builds and deploys production. A push to any other branch is stored, and a preview starts only when someone asks for one.

Before accepting a push, Whisk scans every changed file for passwords and keys with gitleaks and validates whisk.yaml. A push that fails either check is refused with a message saying what to fix. Rewriting the history of the main branch needs an owner or admin.

The repository is standard Git, so anyone with access can clone it and move the code to any other host. A copy can also be kept in the business's own GitHub account with GitHub copy.

Example

A plumbing merchant's stock count app has been changed by two developers and their coding agents over a year. Every change is in the repository's history with its author and date. When one change breaks a report, the developer finds it in the history and fixes it in the next push.

For your coding agent

whisk clone <business>/<app>
cd <app>
git push whisk main

whisk clone names the remote whisk and sets up the credentials, so plain git pull and git push work. Every command is in the CLI reference.