bot docs: pytest gates the release, the website's node tests are advisory

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-11-02 21:55:41 -06:00
parent f8136025ce
commit ca10a9895f
2 changed files with 6 additions and 4 deletions

View File

@@ -134,9 +134,10 @@ message content; Message Content is a privileged intent, enable it only if you n
## 6. Working with the admin ## 6. Working with the admin
- **Source**: push to the community Gitea. CI runs your tests on the `python` runner label, builds the release - **Source**: push to the community Gitea. CI runs on the `python312` runner label (CPython 3.12 plus node),
bundle (§1a), and on `main` installs it on the server. Keep `main` deployable: a red test stops the deploy, builds the release bundle (§1a), and on `main` installs it on the server. Keep `main` deployable: a failing
and a bundle that fails its checksum check is refused. **pytest** run stops the build and the deploy, and a bundle that fails its checksum check is refused. The
website's **node tests are advisory** — a failure is annotated as a warning and blocks nothing.
- **Need infra?** Open a Gitea issue titled `infra: …` stating the exact change: a new env var and why, - **Need infra?** Open a Gitea issue titled `infra: …` stating the exact change: a new env var and why,
a mount, a Caddy path that should skip login (e.g. a public webhook endpoint), a new database. a mount, a Caddy path that should skip login (e.g. a public webhook endpoint), a new database.
Don't work around the proxy or the firewall. Don't work around the proxy or the firewall.

View File

@@ -10,7 +10,8 @@ Your repo's Gitea Actions workflow builds a **release bundle**: one tar.gz holdi
checks its signature and every checksum, swaps it into `/srv/bot/app` (bind-mounted at `/app`, previous checks its signature and every checksum, swaps it into `/srv/bot/app` (bind-mounted at `/app`, previous
release kept for `--rollback`) and restarts the container. The install log comes back in the CI job. release kept for `--rollback`) and restarts the container. The install log comes back in the CI job.
A branch or pull request runs the tests and builds the artifact, and deploys nothing. A branch or pull request runs the tests and builds the artifact, and deploys nothing. The python tests gate the
build; the website's node tests are advisory and only add a warning when they fail.
## Your secrets live in Gitea ## Your secrets live in Gitea