peezy-tech/patch.moi
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
patch.moi/flows/patch-moi-harness
History
matamune e5dd461d41
Record maintenance outcomes from workspace runs
2026-05-16 05:50:00 +00:00
..
exec Record maintenance outcomes from workspace runs 2026-05-16 05:50:00 +00:00
fixtures Add patch maintenance harness flow 2026-05-16 05:40:42 +00:00
schemas Add patch maintenance harness flow 2026-05-16 05:40:42 +00:00
flow.toml Record maintenance outcomes from workspace runs 2026-05-16 05:50:00 +00:00
README.md Record maintenance outcomes from workspace runs 2026-05-16 05:50:00 +00:00

README.md

patch-moi-harness Flow

This flow is the first executable patch.moi maintenance harness. It consumes a generic upstream.release event for peezy-tech/patch-moi-harness, then uses Git state in harness/fork to keep the maintained fork on top of the upstream release tag.

The default behavior is local and reviewable:

  • fetch the configured upstream remote
  • switch to the maintained fork branch
  • rebase onto the release tag when the tag is not already an ancestor
  • run the configured package checks
  • emit candidate branch refs in the FLOW_RESULT artifacts
  • leave pushes disabled unless CODEX_FLOW_PUSH=1 is set

Useful overrides:

CODEX_FLOW_FETCH=0 bun run harness:flow
CODEX_FLOW_PUSH=1 bun run harness:flow

The fixture event is fixtures/upstream-release-v0.1.3.json. It should be a no-op rebase against the current harness fork while still verifying the package surface and reporting the local maintained branch as the candidate ref.