Creating issue failed: No matching repository (name for source repo of my fork) found for (name of source user for my fork)

[Esterni]

Issue Type: Bug

Currently working on a fork that has since been renamed. Attempting to create an issue using any method (# TODO, Create Issue..., Create issue from selection...) gives a notification that no matching repos were found, but the names given are for the original repo and author names.

Unsure of the steps to reproduce specifically. I'm fairly new to using git overall, but have had guidance from someone more experienced. I'm told there's nothing particularly special about how I'm working with this.

Extension version: 0.17.0
VS Code version: Code 1.47.0 (d5e9aa0227e057a60c82568bf31c04730dc15dcd, 2020-07-09T08:02:06.629Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz (4 x 2594)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	7.88GB (1.79GB free)
Process Argv
Screen Reader	no
VM	0%

[alexr00]

@Esterni I think you need to update your remotes. What is the output of git remote -v in your repo? Does it show the original name or the rename?

[Esterni]

@alexr00 since creating this issue I've moved the project into it's own repo. My apologies for not being able to provide more information or troubleshooting on this

[sunt05]

The issue here: I'm working on a forked repo and archived the upstream one; it seems this plugin always tries to create issues in the upstream repo and thus fails.

My repos with issues are the following:

1. new one (origin): https://github.com/UMEP-dev/SUEWS
2. old/archived one (upstream): https://github.com/Urban-Meteorology-Reading/SUEWS

Thanks for your help!

[alexr00]

@sunt05 can you try adding this setting

	"githubPullRequests.remotes": [
		"origin"
	],

By default, we try to be smart and look for an upstream repo. This setting should cause upstream to be ignored.

[sunt05]

@sunt05 can you try adding this setting

	"githubPullRequests.remotes": [
		"origin"
	],

By default, we try to be smart and look for an upstream repo. This setting should cause upstream to be ignored.

Thanks for following up this issue.
The above, however, doesn't work; I have even tried to remove the upstream remote with a freshly cloned repo, no success either.

I'm happy to provide more diagnostic info if needed: I really like this feature and would like to use it in a forked repo.