Skip to content

repo-hygiene: fleet preflight has no no-upstream classification — never-pushed branches invisible in ahead/behind reporting #998

Description

@kyle-sexton

Problem

Preflight-style reporting (rev-list --count @{upstream}..HEAD) yields - for branches with no upstream; 111 of 82 repos' rows in a field sweep were ahead=-, so "N unpushed commits" claims silently cover only with-upstream branches. Never-pushed local work is exactly what a cleanup skill must not miss.

Fix direction

Classify no-upstream branches separately and check them via git cherry / rev-list against the default branch; surface "no upstream, M commits not on origin/" as its own preflight class. Also consider whether the preflight belongs in repo-fleet-hygiene:audit and repo-hygiene consumes it (the session hand-rolled preflight despite that skill existing — either a use-your-skills miss or a coverage gap there).

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: lowNice-to-have, cosmetic, or speculative; opportunistic.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions