Skip to content

Conversation

@gunadhya
Copy link
Contributor

@gunadhya gunadhya commented Feb 9, 2026

Fixes #12575
Reuse an existing linked branch (same name + repo) instead of failing when it already exists

In developRunCreate, when --name is provided:

  1. Look up linked branches for the issue
  2. Reuse a matching branch if it exists
  3. Only create a new linked branch if no match is found

@gunadhya gunadhya force-pushed the fix-repeating-cmd-gh-issue-develop branch from 4f5cc42 to bee197c Compare February 9, 2026 18:00
@gunadhya gunadhya force-pushed the fix-repeating-cmd-gh-issue-develop branch 2 times, most recently from 1a95ac4 to b38f677 Compare February 9, 2026 18:09
@gunadhya gunadhya marked this pull request as ready for review February 9, 2026 18:38
@gunadhya gunadhya requested a review from a team as a code owner February 9, 2026 18:38
@gunadhya gunadhya requested a review from BagToad February 9, 2026 18:38
@cliAutomation cliAutomation added the external pull request originating outside of the CLI core team label Feb 9, 2026
@BagToad BagToad changed the title issue develop: prevent .git/config corruption on repeated --name invocation issue develop: prevent .git/config corruption on repeated --name invocation Feb 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

external pull request originating outside of the CLI core team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Repeating the command gh issue develop twice breaks config

2 participants