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:
@@ -134,9 +134,10 @@ message content; Message Content is a privileged intent, enable it only if you n
|
||||
|
||||
## 6. Working with the admin
|
||||
|
||||
- **Source**: push to the community Gitea. CI runs your tests on the `python` runner label, builds the release
|
||||
bundle (§1a), and on `main` installs it on the server. Keep `main` deployable: a red test stops the deploy,
|
||||
and a bundle that fails its checksum check is refused.
|
||||
- **Source**: push to the community Gitea. CI runs on the `python312` runner label (CPython 3.12 plus node),
|
||||
builds the release bundle (§1a), and on `main` installs it on the server. Keep `main` deployable: a failing
|
||||
**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,
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user