Skip to content

Creating PR cannot determine remote branch name #10862

Closed
#10863
Closed
Creating PR cannot determine remote branch name#10862
#10863
Labels
bugSomething isn't workinggh-prrelating to the gh pr commandpriority-2Affects more than a few users but doesn't prevent core functions

Description

@cs278
cs278
opened on Apr 24, 2025

Describe the bug

Using gh pr create to create a new pull request fails whereas previously it worked.

Affected version

Please run gh version and paste the output below.

gh version 2.71.1 (2025-04-24)
https://github.com/cli/cli/releases/tag/v2.71.1

Steps to reproduce the behavior

  1. Create new branch
  2. Create a commit
  3. Run gh pr create
  4. See error could not determine remote branch name

Expected vs actual behavior

I expect to be asked to provide the pull request details e.g. title.

Logs

Paste the activity from your command line. Redact if needed.

$ GH_DEBUG=true gh pr create --assignee cs278 
[git remote -v]
[git config --get-regexp ^remote\..*\.gh-resolved$]
* Request at 2025-04-24 16:28:54.65877698 +0100 BST m=+0.201817171
* Request to https://api.github.com/graphql
* Request took 401.056089ms
[git status --porcelain]
[git symbolic-ref --quiet HEAD]
[git config --get-regexp ^branch\.issue/8670-update-docs\.(remote|merge|pushremote|gh-merge-base)$]
[git rev-parse --symbolic-full-name issue/8670-update-docs@{push}]
[git config push.default]
could not determine remote branch name

Activity

  1. cs278
    added
    bugSomething isn't working
    on Apr 24, 2025
  2. cliAutomation
    added
    needs-triageneeds to be reviewed
    on Apr 24, 2025

  3. williammartin commented on Apr 24, 2025

    @williammartin
    williammartin
    on Apr 24, 2025
    Member

    Hey @cs278, sorry for the inconvenience.

    I think you're running into an issue here because you have push.default set to tracking or upstream but you don't have a remote tracking branch set.

    What's the output of git config push.default and git config get branch.issue/8670-update-docs.merge

  4. williammartin
    added
    more-info-neededMore info needed from user/contributor
    gh-prrelating to the gh pr command
    on Apr 24, 2025

  5. cs278 commented on Apr 24, 2025

    @cs278
    cs278
    on Apr 24, 2025
    Author

    What's the output of git config push.default and git config get branch.issue/8670-update-docs.merge

    $ git config push.default
upstream
$ git config get branch.issue/8670-update-docs.merge;echo $?
1

  6. williammartin commented on Apr 24, 2025

    @williammartin
    williammartin
    on Apr 24, 2025
    Member

    Thanks. Are you working on a fork here, or just a single repo?

  7. williammartin
    linked a pull request that will close this issueFix pr create when push.default tracking and no merge ref #10863on Apr 24, 2025

  8. cs278 commented on Apr 24, 2025

    @cs278
    cs278
    on Apr 24, 2025
    Author

    single repo

    But I do have multiple remotes if that makes a difference.

  9. williammartin commented on Apr 24, 2025

    @williammartin
    williammartin
    on Apr 24, 2025
    Member

    I believe this is fixed in #10859, if you'd be up for confirming it you can follow our instructions to build from source. It would be much appreciated 🙏

  10. williammartin
    added
    priority-2Affects more than a few users but doesn't prevent core functions
    and removed
    more-info-neededMore info needed from user/contributor
    needs-triageneeds to be reviewed
    on Apr 24, 2025
  11. BagToad
    closed this as completedin #10863on Apr 24, 2025
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

    bugSomething isn't workinggh-prrelating to the gh pr commandpriority-2Affects more than a few users but doesn't prevent core functions

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions