Skip to content

show link to issue in cannot close issue warning case #193

Closed

Description

@JacobStephens2

thirdshift: warning: could not close issue #177, so if it is still open, close it by hand: gh issue close 177 --repo JacobStephens2/thirdshift --comment 'Closed by #184, merged into main by a thirdshift Merge run.'
thirdshift: cleaning up the worktree and local branch issue-177

Activity

  1. JacobStephens2 commented on Oct 17, 2026

    @JacobStephens2
    OwnerAuthor

    This was generated by AI during triage.

    Agent Brief

    Category: enhancement
    Summary: Include the Issue URL in the warning when closing an issue after Self-merge fails.

    Current behavior:
    After a confirmed Self-merge, a failure to close the issue produces a warning naming only its number and a manual gh issue close command. The full Issue URL is already known.

    Desired behavior:
    Include the full Issue URL in that warning so the Day shift can open the affected issue directly. Keep the existing manual close command and its repository and explanatory comment.

    Key interfaces:

    • IssueUrl: supplies the full URL and repository-qualified identity.
    • Delivery's post-Self-merge cleanup warning: display the URL when closing the issue fails.

    Acceptance criteria:

    • When an issue-close attempt fails after a confirmed Self-merge, the warning contains the full URL of that issue.
    • The warning retains a correct manual close command for the same issue and repository.
    • An already closed issue does not produce a spurious close-failure warning; a cleanup failure remains a warning and does not reverse the confirmed merge outcome.
    • Relevant delivery coverage verifies the warning identifies the correct issue.

    Out of scope:

    • Changing Claim warnings, branch-deletion warnings, cleanup retry policy or merge behavior.
    • Adding configuration or changing other error messages.
  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