Skip to content

docs: say that every web PR touching the catalog, the deploy path or a guide has a counterpart here #178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
GeiserX merged 1 commit into from
Oct 12, 2026
Merged

docs: say that every web PR touching the catalog, the deploy path or a guide has a counterpart here #178

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,16 @@ go test ./... # run Go tests
- SQLite migrations are forward-only (no down migrations)
- Frontend Wails bindings auto-generated — do not edit `frontend/wailsjs/` manually

## The web repository leads, and this one follows

`services/` is vendored from [GeiserX/CashPilot](https://github.com/GeiserX/CashPilot) (`make catalog-sync SRC=../CashPilot`; the Desktop-only deltas live in `catalog-overlay/`). The deploy form (`frontend/src/render/fields.ts`), the deploy validation (`validateRequired` in `internal/services/manager.go`) and the catalog's facts are re-implemented here. So a web PR that touches `services/`, the deploy route in `app/main.py`, the env fields in `app/static/js/app.js` or a guide has a counterpart here, and whoever merges the web PR owns it in the same session:

1. `make catalog-check SRC=../CashPilot`. If a new live image has no pin, resolve its digest into `catalog-overlay/image-pins.yml` first. Then `make catalog-sync SRC=../CashPilot`, review the diff, commit it.
2. Port a behaviour change to `internal/services` and `frontend/src/render`, with its test.
3. Close the standing "Catalog drift" issue once the check passes.

The weekly `catalog-drift.yml` run is the backstop, not the plan: it sees the catalog and never a behaviour change.

## Testing

```bash
Expand Down
Loading