Alex Ross

@Yash621 not yet!

@saifahn, as far as I know https://github.com/microsoft/vscode-pull-request-github/issues/2426 is still a problem. If you want to take a crack at it please do!

It looks like there's a lot of time spent in the built in git extension, which this extension does rely on. Next time it happens, can you also share the...

👍 thanks @parched

I took a look at where all those git calls could be coming from in this extension, and it looks like they should only occur when you open a file/diff....

@parched sorry for the slow response on this. Can you set `"githubPullRequests.logLevel": "debug"` in your settings, reproduce the issue, then share the output of GitHub Pull Request again?

We might be able to use the `updatePullRequest` GraphQL API mutation to set the `closingIssuesReferences`.

`updatePullRequest` doesn't let you set `closingIssuesReferences`. An alternative would be to automatically include the "fix #123" string in the description.

Since there is no GitHub API to link PRs and issues, I've taken the approach of adding the #123 in the PR description. This feels like a work around, and...

To verify: - Make a commit that has a reference to an issue number in the same repo in the first line of the commit (see the screenshot at the...