Skip to content

tell user how to push the branch / give a sample command when base branch does not exist on origin #295

Closed

Description

@JacobStephens2

[jstephens@dev html]$ thirdshift https://github.com/Educational-Travel-Adventures/tourbot/issues/1328
thirdshift: 14:01:07 base branch feature/call-pop-resnum-order does not exist on origin; push it first
[jstephens@dev html]$

Activity

  1. JacobStephens2 commented on Oct 17, 2026

    @JacobStephens2
    OwnerAuthor

    This was generated by AI during triage.

    Agent Brief

    Category: enhancement
    Summary: Give an actionable command when the Base branch is missing on origin.

    Current behavior:
    Base branch preparation reports that the branch does not exist on origin and says to push it first, without showing a command. A directly started Run normally uses the checked-out branch; a Pass may name a different Base branch, including one that does not exist locally.

    Desired behavior:
    Keep the preflight failure and identify the missing Base branch. When that exact branch exists locally, include a copyable command that pushes it to origin and sets its upstream, equivalent to git push --set-upstream origin <base>, with safe argument quoting. When it does not exist locally, explain that the named branch must first be created or obtained, or a valid Base branch selected; do not suggest pushing the unrelated checked-out branch.

    Key interfaces:

    • Base branch preparation: knows the selected branch, origin and local branch presence.
    • The existing preflight error and documented Base branch guidance: provide consistent recovery instructions.

    Acceptance criteria:

    • A missing remote Base branch that exists locally produces an error containing a usable push command for that exact branch and origin.
    • A Pass naming a branch other than the checked-out branch receives guidance for the named branch.
    • A branch absent both locally and on origin receives accurate guidance rather than a command that publishes a different branch or cannot work as presented.
    • Preflight performs no push, checkout, branch creation or other automatic repair.
    • Relevant preflight coverage exercises local-present and local-absent cases; documented examples quoted by the change are kept consistent.

    Out of scope:

    • Other branch or Worktree error messages, including the local-ahead-of-origin case.
    • New flags, configuration or automatic branch repair.
  2. added
    enhancementNew feature or request
    ready-for-agentFully specified, ready for an AFK agent
    in-progressA Claim: thirdshift has taken this issue
    and removed
    ready-for-agentFully specified, ready for an AFK agent
    on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions