Invited publishers can use the Puls CLI in CI to stage a browser-game release. Get CLI installation instructions from Puls before setting up your runner.

Set Up Your API Key#

Add your Puls API key as a secret in your CI environment. In GitHub, go to Settings → Secrets → Actions and create a secret called PULS_TOKEN.

Stage a Release#

Install the CLI on your runner using the instructions provided with your invitation. Set PULS_TOKEN from your CI secret, build the game, then run:

puls deploy my-game --dir ./build --version v1.0.0

This stages the release and gives you a test link. It does not change the live game. After testing, publish it with puls releases publish my-game v1.0.0. Only automate the publish step if you want every successful build to go live.

Tips#

• Use --prune if you want CI to remove the oldest inactive release before uploading
• Name your versions after git tags or commit hashes for easy identification:

  puls deploy my-game --version $GITHUB_SHA

• Use --dry-run in pull request checks to confirm the build folder exists and see its file count and size; it does not test a deployment

Next: Troubleshooting