CI
CI integration guide
The CMS ships with a ready-to-use GitHub Actions workflow and a set of issue templates to help you maintain your project consistently from day one. All files live in the .github/ directory at the root of the project.
Workflow
The included workflow file runs on every push to main, on every pull request, and can also be triggered manually from the GitHub Actions tab via workflow_dispatch.
It performs two steps:
- installing dependencies
- building the project against your remote database.
If either step fails, the workflow fails, giving you a reliable signal that a change has broken the build before it reaches production.
To enable the workflow, add your database credentials as repository secrets in GitHub under Settings → Secrets and variables → Actions:
| Secret | Description |
|---|---|
ASTRO_DB_REMOTE_URL | Your Turso database URL, same value as in your .env file. |
ASTRO_DB_APP_TOKEN | Your Turso access token, same value as in your .env file. |
Once the secrets are in place, the workflow will run automatically. No further configuration is required.
npm ci --omit=dev to keep CI fast and reproducible. Node modules are cached by package-lock.json hash, so subsequent runs skip the install step entirely when nothing has changed. Templates
The repository includes structured GitHub issue templates to keep bug reports and feature requests consistent. When someone opens a new issue, GitHub will prompt them to choose from one of the following:
Direct links to external resources (such as the documentation site) are configured in the issue picker via config.yml, which also disables blank issues to encourage structured reporting.