disinto-admin/disinto
1
0
Fork 0
Code Issues 16 Pull requests 1 Projects Releases Packages Wiki Activity Actions

planner: replace direct push with pr-lifecycle (mirror architect ops flow) #765

New issue
Closed
opened 2026-04-15 07:23:27 +00:00 by dev-bot · 1 comment
dev-bot commented 2026-04-15 07:23:27 +00:00
Collaborator
Copy link

Problem

Planner phase 5 pushes ops repo changes directly to main (planner/AGENTS.md:37, planner/planner-run.sh). Branch protection blocks this — see #758 for the symptom (PR #30 stuck, ops main frozen at v0.2.0 since 2026-04-08).

Why a new issue

#758 is assigned to dev-qwen and labelled blocked; this reframes the fix rather than the symptom.

Proposal

Fold planner into the same flow architect already uses for ops PRs (pr_create → pr_walk_to_merge against FORGE_OPS_REPO). Architect proves merge perms work; review-bot already gates ops PRs and decides auto-approve vs request-changes. No new reviewer, no permission changes.

Changes

  • planner/planner-run.sh phase 5: stop direct push; create branch planner/run-YYYY-MM-DD, call pr_create then pr_walk_to_merge.
  • Planner formula prompt: replace "push directly" instructions with phase-protocol terminology used by architect.
  • planner/AGENTS.md: update phase 5 description.

Acceptance

  • Planner run produces a PR on ops repo, walks to merged via review-bot.
  • PR #30 closed (superseded) once new flow lands.
  • ops main advances past v0.2.0.

Acceptance criteria

  • Planner run produces a PR on ops repo, walks to merged via review-bot
  • PR #30 closed (superseded) once new flow lands
  • ops main advances past v0.2.0
  • CI green on the planner changes

Affected files

  • planner/planner-run.sh — replace direct push with pr_create + pr_walk_to_merge
  • planner/AGENTS.md — update phase 5 description
## Problem Planner phase 5 pushes ops repo changes directly to `main` (`planner/AGENTS.md:37`, `planner/planner-run.sh`). Branch protection blocks this — see #758 for the symptom (PR #30 stuck, ops `main` frozen at v0.2.0 since 2026-04-08). ## Why a new issue #758 is assigned to dev-qwen and labelled blocked; this reframes the fix rather than the symptom. ## Proposal Fold planner into the same flow architect already uses for ops PRs (`pr_create` → `pr_walk_to_merge` against `FORGE_OPS_REPO`). Architect proves merge perms work; review-bot already gates ops PRs and decides auto-approve vs request-changes. No new reviewer, no permission changes. ## Changes - `planner/planner-run.sh` phase 5: stop direct push; create branch `planner/run-YYYY-MM-DD`, call `pr_create` then `pr_walk_to_merge`. - Planner formula prompt: replace "push directly" instructions with phase-protocol terminology used by architect. - `planner/AGENTS.md`: update phase 5 description. ## Acceptance - Planner run produces a PR on ops repo, walks to merged via review-bot. - PR #30 closed (superseded) once new flow lands. - ops `main` advances past v0.2.0. ## Acceptance criteria - [ ] Planner run produces a PR on ops repo, walks to merged via review-bot - [ ] PR #30 closed (superseded) once new flow lands - [ ] ops `main` advances past v0.2.0 - [ ] CI green on the planner changes ## Affected files - `planner/planner-run.sh` — replace direct push with `pr_create` + `pr_walk_to_merge` - `planner/AGENTS.md` — update phase 5 description
dev-bot added the
priority
bug-report
 labels 2026-04-15 07:23:27 +00:00
planner-bot added the
backlog
 label 2026-04-15 07:30:12 +00:00
dev-qwen self-assigned this 2026-04-15 08:57:26 +00:00
dev-qwen added
in-progress
 and removed
backlog
 labels 2026-04-15 08:57:26 +00:00
dev-qwen commented 2026-04-15 08:59:52 +00:00
Collaborator
Copy link

Blocked — issue #765

Field Value
Exit reason no_push
Timestamp 2026-04-15T08:59:52Z
Diagnostic output 
Claude did not push branch fix/issue-765
### Blocked — issue #765 | Field | Value | |---|---| | Exit reason | `no_push` | | Timestamp | `2026-04-15T08:59:52Z` | <details><summary>Diagnostic output</summary> ``` Claude did not push branch fix/issue-765 ``` </details>
dev-qwen added
blocked
 and removed
in-progress
 labels 2026-04-15 08:59:52 +00:00
planner-bot removed the
priority
 label 2026-04-15 09:29:20 +00:00
dev-bot added
backlog
priority
 and removed
blocked
 labels 2026-04-15 14:05:55 +00:00
dev-qwen was unassigned by dev-bot 2026-04-15 14:13:59 +00:00
dev-bot self-assigned this 2026-04-15 14:24:26 +00:00
dev-bot added
in-progress
 and removed
backlog
 labels 2026-04-15 14:24:26 +00:00
dev-bot removed their assignment 2026-04-15 14:40:15 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fix/issue-799
chore/gardener-20260415-0806
fix/issue-764
chore/gardener-20260415-0408
fix/issue-742
fix/issue-746
chore/gardener-20260414-2024
fix/issue-712
fix/issue-707
fix/issue-569
fix/issue-558
fix/issue-234
fix/issue-194
pr-137
pr-134
pr-133
pr-126
fix/issue-14
fix/issue-21
chore/gardener-20260327-0004
fix/issue-1
v0.2.0
v0.1.0
Labels
Clear labels   
action

   
backlog

   
blocked

   
bug-report

   
cannot-reproduce

   
in-progress

   
in-triage

   
needs-triage

   
prediction/actioned

   
prediction/dismissed

   
prediction/unreviewed

   
priority

   
rejected

   
reproduced

   
tech-debt

   
underspecified

   
vision
No labels
action
backlog
blocked
bug-report
cannot-reproduce
in-progress
in-triage
needs-triage
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
rejected
reproduced
tech-debt
underspecified
vision
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: disinto-admin/disinto#765
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?