open/portfolio-optimiser
1
0
Fork 0
Code Issues Releases 3 Activity

docs(shared): S4 — sync policy is pull-only (subtree push leaks consumer history)

Browse source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AaQCFnfsh3tfq1VfzdJpoi
This commit is contained in:
Kjell Tore Guttormsen 2026-07-03 05:42:25 +02:00
commit 80c1df5ae7
1 changed files with 10 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

23
shared/README.md
View file

@ -42,24 +42,21 @@ so the only thing that differs is the agent framework itself.
at this unchanged `shared/` path (so tests and the `PORTFOLIO_SHARED_ROOT` default at this unchanged `shared/` path (so tests and the `PORTFOLIO_SHARED_ROOT` default
resolver are unaffected). Do not edit commons content anywhere else without syncing. resolver are unaffected). Do not edit commons content anywhere else without syncing.
## Subtree sync (run from the consuming repo's root) ## Subtree sync (pull-only — run from the consuming repo's root)
The remote is registered as `commons` The remote is registered as `commons`
(`ssh://git@git.fromaitochitta.com/ktg/portfolio-optimiser-commons.git`). (`ssh://git@git.fromaitochitta.com/ktg/portfolio-optimiser-commons.git`).
- **Pull** upstream changes from commons into this repo: **All edits land in commons first** (clone it, commit, push there), then each
consuming repo pulls them in:
```sh ```sh
git subtree pull --prefix=shared commons main --squash git subtree pull --prefix=shared commons main --squash
``` ```
- **Push** local `shared/` edits (committed here first) back to commons: **Never run `git subtree push` from a consuming repo.** Observed 2026-07-03: because
this repo's history contains commits that create/delete the `shared/` prefix, the
```sh push re-split leaked the consumer's *entire* history into commons (cleaned up by
git subtree push --prefix=shared commons main force-push the same day). Pull-only keeps commons the clean source of truth.
```
Edits should preferably land in commons first and be pulled; pushing from a consumer
is for small fixes made in place. Either way, commons remains the source of truth.
See the target picture for the full architecture: `docs/plan/2026-06-26-maalbilde-agentic-loop.md`. See the target picture for the full architecture: `docs/plan/2026-06-26-maalbilde-agentic-loop.md`.