pull-all: report unpushed commits on the default branch instead of up to date #287

New issue

Open

opened 2026-10-22 05:40:15 +01:00 by vnprc-agent · 0 comments

vnprc-agent commented

2026-10-22 05:40:15 +01:00

Contributor

pull-all reports a checkout whose default branch carries unpushed commits as up to date, so a stale local master goes unnoticed until the next patch relay conflicts with it.

Primary goals:

Unpushed is a state, on any branch — a repository whose current branch is ahead of its upstream prints unpushed with the count, the way one on a side branch already does, instead of up to date.
Skip stays explicit — the pull is skipped for that repository as it is today for a dirty one, and the summary line says why.

Current state

Today a repository on master with local commits not on origin/master prints up to date after pull-all, while the same condition on an agent branch prints skipped [on <branch> — N unpushed commits]. Five public checkouts on the hypervisor sat in that state after an earlier relay and were reported healthy; the next allod patch receive into them hit conflicts on two and no-ops on three.

Scope

In: pull-all in allod/tools and its test. Out: the relay tools themselves.

`pull-all` reports a checkout whose default branch carries unpushed commits as up to date, so a stale local master goes unnoticed until the next patch relay conflicts with it. Primary goals: - **Unpushed is a state, on any branch** — a repository whose current branch is ahead of its upstream prints `unpushed` with the count, the way one on a side branch already does, instead of `up to date`. - **Skip stays explicit** — the pull is skipped for that repository as it is today for a dirty one, and the summary line says why. ### Current state Today a repository on `master` with local commits not on `origin/master` prints `up to date` after `pull-all`, while the same condition on an agent branch prints `skipped [on <branch> — N unpushed commits]`. Five public checkouts on the hypervisor sat in that state after an earlier relay and were reported healthy; the next `allod patch receive` into them hit conflicts on two and no-ops on three. ### Scope In: `pull-all` in `allod/tools` and its test. Out: the relay tools themselves.

vnprc-agent referenced this issue from allod/strategy

2026-10-22 05:47:09 +01:00

Sandbox every delegated worker inside its dev VM so one VM runs a swarm #69