Change:
return false; } <del> const match = /^(?:https://github.com/|git@github.com:)([^/]+)/([^/.]+)(?:.git)?$/i.exec(remoteUrl); </del> <ins> const match = /^(?:https://github.com/|git@github.com:)([^/]+)/([^/.]+)/i.exec(remoteUrl); </ins> if (!match) { return false; }

Discussion:
For step 4 of , when I try publishing the branch, I get the error "Git: remote: Permission to joaomoreno/test-pr- denied to rzhao271." There is no option to create a fork: ! Originally posted by in
says: I got the same issue on the latest Insiders <img width="1202" alt="image" src="https://user-"Command output: Remote URL:
Can you give me exact steps?
I think I figured it out:
Verification: and clone a branch a change to and commit to push/publish that branch. Code should tell you that you can't push to that repo and will offer to fork the repository, accept.

From in
Can't verify this because I'm no longer prompted to create a fork when I push to a repo that I don't have write access to.

<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --Use to create if exists in directory. Not just using latest commit to create .
Are you using an extension which adds the ability to create a PR? If so, please report the issue on the extension repo. The Report Issue dialog from VS Code's Help menu may be able to assist you. /needsMoreInfo
Yes, after recheck,it's a feature of extension,which seems to be a builtin exttension.
Can you give me the full name of the extension? Maybe a screenshot of it in the product? Or the view where you can create a PR?
The full name is exactly <img src="https://user-" alt="drawing" width="200"/Here is I create Pr !
I'd like to fix it. Any leads are appreciated.
Sure, this would be a great starting point:
Verification: and clone a branch a change to and commit to push/publish that branch. Code should tell you you can't push to that repo and will offer to fork the repository, accept. should then ask you whether you'd like to create a PR, accept. You should get shown exactly 9 PR templates to choose from. Reference:
I tried but after selecting a repository to fork (which then successfully creates a fork on Github) nothing is pushed without any error message. However, the developer console and the Git extension logs show this: ! It seems the source of the problem lies when calling : Maybe no rename occurs when calling (with no exception thrown).
Very strange, can you easily reproduce? Delete your fork and try again.
Yes. I checked it several times and the results were the same.
I did get the list of PR templates: ! However, I had no way to get back to the picker after taking that screenshot (which dismissed the picker). At minimum I feel we should use , since the Create PR functionality is not exposed as a command palette command, I am stuck. Additionally, after I selected a template to create the PR, nothing happened. Finally, it was unexpected that I get two popups to create a PR when the GitHub Pull Requests and Issues extension is installed: !
You mean no PR was created, right?

Nonetheless, I think the Github extension needs more visible error messages (e.g., via notifications).
Yes, no PR was created (I checked on GitHub).
Created two issues from the discoveries. Thanks!
Actually three. Creating a PR just doesn't work at all anymore:
For step 4, when I try publishing the branch, I get the error "Git: remote: Permission to joaomoreno/test-pr- denied to rzhao271." There is no option to create a fork: !
Is the Github extension enabled for you?
Just confirmed that it's enabled for me.
Can you file a separate issue?
Verification of this issue fails since the user is no longer prompted to create a PR as found in :/
Wait you hit this too? I totally can't repro, that's why I asked to follow up with a separate issue. We can move this to May just for verification sake.
Yeah I hit the same thing as
I just tried testing this: On pushing the new branch, I get ! and then: !
Reopening due to comment but feel free to do what you want with this
I got the same issue on the latest Insiders <img width="1202" alt="image" src="https://user-"Command output: Remote URL:
this is
Moving verification to July to account for