Connect GitHub
Run the connect command
Authorize in the browser
Sign in to GitHub (if you are not already) and approve the authorization. The browser redirects back to your terminal automatically.
Auto-deploy on push
Once GitHub is connected, every push to your default branch (usuallymain) triggers a new deployment automatically. The flow looks like this:
- You push code to GitHub
- Nometria detects the push via webhook
- Your app is rebuilt and redeployed
- The new version is live in about 2 minutes
Only pushes to the branch configured in your Nometria project trigger deploys. Pushes to other branches are ignored unless you configure them in the dashboard.
Push changes from the CLI
If you want to commit and push in one step, the CLI has a shortcut:List connected repos
See which repos are linked to your account:GitHub Actions workflow
For more control over the deployment process, you can use a GitHub Actions workflow instead of (or in addition to) the webhook-based auto-deploy. Runnom setup to generate the workflow file automatically:
.github/workflows/nometria-deploy.yml:
Set up the secret
Get your API key
Go to nometria.com/settings/api-keys and generate a key (or copy an existing one).
Add it to GitHub
In your GitHub repo, go to Settings > Secrets and variables > Actions and create a new secret called
NOMETRIA_API_KEY with your key as the value.Manual deploys
The workflow includesworkflow_dispatch, which means you can also trigger it manually from the Actions tab in GitHub. This is useful when you want to redeploy without pushing new code.
Troubleshooting
GitHub connect opens the browser but nothing happens
GitHub connect opens the browser but nothing happens
Make sure you are signed in to your Nometria account first:Then try
nom github connect again.Pushes are not triggering deploys
Pushes are not triggering deploys
Check that the connection is active:If it says “not connected”, run
nom github connect again. Also verify you are pushing to the correct branch.GitHub Actions workflow fails
GitHub Actions workflow fails
Check that the
NOMETRIA_API_KEY secret is set correctly in your repo settings. You can also add NOM_DEBUG=1 to the env block to get more detailed output: