a digital entity named phi that roams bsky phi.zzstoatzz.io
2
fork

Configure Feed

Select the types of activity you want to include in your feed.

switch deploy trigger from push-to-main to v* tags

just release <version> to tag and deploy. just deploy for manual.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

zzstoatzz f811181a 82ebc0d0

+9 -4
+2 -2
.tangled/workflows/deploy.yml
··· 1 1 when: 2 - - event: ["push"] 3 - branch: main 2 + - event: push 3 + tag: "v*" 4 4 5 5 engine: nixery 6 6
+1 -1
CLAUDE.md
··· 36 36 37 37 ## deployment 38 38 39 - fly.io app `zzstoatzz-phi`. every push to main triggers `.tangled/workflows/deploy.yml` — this means even doc-only changes cause a deploy. consider switching to tag-based triggers (like zat uses `tag: "v*"`) or adding a separate CI workflow for tests. 39 + fly.io app `zzstoatzz-phi`. deploys are triggered by `v*` tags, not pushes to main. to deploy: `just release <version>` (e.g. `just release 0.2.0`) or `just deploy` for manual fly.io deploy without tagging. 40 40 41 41 ## key architecture 42 42
+6 -1
justfile
··· 18 18 evals-memory: 19 19 uv run pytest evals/test_memory_integration.py -v 20 20 21 - # deployment 21 + # deployment — CI deploys on v* tags, `just deploy` for manual 22 22 deploy: 23 23 flyctl deploy 24 + 25 + # tag and push a release (triggers CI deploy) 26 + release version: 27 + git tag "v{{version}}" 28 + git push origin "v{{version}}" 24 29 25 30 # code quality 26 31 fmt: