You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(publish): accept→publish by default + publish visibility (#97)
After an accept, whether a draft PR actually opened was invisible: a standalone
`pdca signoff --accept` recorded §9 and stopped at COMPLETE with no publish, and
flow's auto-publish dropped failures silently — so "approved but unpublished" went
unnoticed (observed: five COMPLETE bundles, no PRs, no signal).
Per the issue's preferred direction (unify command behaviour, mirroring the
flow/batch unification):
- `pdca signoff --accept` now PUBLISHES on accept by default (dry-run when the
publisher leaf is stubbed), with `--no-publish` to opt out — so an unpublished
accepted bundle only exists when asked for, never silently.
- flow's publish-on-accept is LOUD on failure: both flow.flow and the batch
_drive_and_act path check publish's return and warn (COMPLETE but NOT published —
run `pdca publish <id>`) instead of swallowing a non-zero rc.
- `pdca status` (and bare `pdca`) surfaces each COMPLETE bundle's publish state via
_publish_flag: `[PR <url>]` (publish.json with a url), `[unpublished]`
(dry-run/no-target/failed/not-yet-run), `[close: no PR]` (empty/no patch).
Tests: PublishOnAccept — accept publishes by default; --no-publish opts out; a
publish failure is surfaced (rc + loud); status flag for published/unpublished/
close. Suite green (159).
Closes#97.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Eduard Ralph <15236434+eduralph@users.noreply.github.com>
0 commit comments