Automatic deployments

Inhank Cloud can automatically deploy your service every time you push to its tracked branch, so production stays in sync with your code without you having to click anything.

How it works

When you create a service, you pick a Git branch (often main or production). That's your service's tracked branch.

Inhank Cloud subscribes to push events on this branch via your GitHub installation. When a new commit lands:

1. A new deployment is queued with the new commit's hash.
2. The deployment runs through the normal pipeline: build → release.
3. Your service goes live with the new version.

If a build fails, your live version stays untouched. The failed deployment appears in the service's Deployments tab so you can investigate.

Changing the tracked branch

To deploy from a different branch:

1. Open your service.
2. Go to Settings → Source.
3. Change the Branch field.
4. Click Save.

Inhank Cloud immediately starts deploying pushes to the new branch. Pushes to the old branch no longer trigger anything.

Disabling automatic deployments

If you'd rather control deployments by hand:

1. Open your service.
2. Go to Settings → Deployments.
3. Toggle Automatic deployments off.

Now pushes to the tracked branch are recorded (for your reference), but nothing is built or released until you click Deploy.

This is useful when:

• You have a separate staging environment and only want to ship after testing there.
• You batch multiple commits into one deployment to save build minutes.
• You're in the middle of a long-running migration.

Skipping a deploy with a commit flag

Add [skip ci] (or [ci skip]) anywhere in your commit message to tell Inhank Cloud to ignore that push.

git commit -m "docs: tweak README [ci skip]"

Useful for docs-only changes that don't need a redeploy.

Concurrent push handling

If multiple commits land in rapid succession, only the latest one is deployed. Inhank Cloud cancels any in-flight build that's been superseded by a newer commit, so you don't waste build minutes shipping intermediate states.

If you push two commits 30 seconds apart, you'll see the first deployment show Cancelled and the second one run normally.

Pull requests and preview deployments

Preview deployments for pull requests are not supported in yet now.

For now:

• Use your tracked branch (typically main or production) for live traffic.
• Create separate services for staging and development environments, each tracking the matching branch.

Limits

• One automatic deployment per push.
• If your wallet balance is insufficient to renew your plan, automatic deployments are paused until you top up. See Billing.

What's next