Does not work if the GitHub remote is not called origin

[qc00]

To Reproduce
Steps to reproduce the behavior:

1. Clone GitHub repo and open in VS Code
2. Verify GitHub extensions work
3. git remote rename origin fork
4. Reload Window/restart app
5. Verify other GitHub extensions like PR still work
6. Actions extension displays: no GitHub repositories found

Expected behavior
The Actions extension continues to work (like the other extensions from GitHub) or provides an option to select a remote.

Extension Version
v0.25.5

[muzimuzhi]

typo in issue title: "if the GitHub branch is not called origin" -> "if the Git remote is not called origin"

[muzimuzhi]

Looks like for now you have to change config github-actions.remote-name per (vscode) project by hand.

[qc00]

That worked. Thanks!

Ideally, this can be detected automatically like the other GitHub extensions

[muzimuzhi]

A list of remote names could be provided but user still need to make a choice if multiple remotes exist and several of them are cloned from github.

[muzimuzhi]

A list of remote names could be provided but user still need to make a choice if multiple remotes exist and several of them are cloned from github.

I mean, in simple cases yes the remote could be automatically used, but in more general cases there might be multiple qualified remotes (typically an upstream and a fork). In the latter case perhaps the extension could provide an easier way to switch between remotes.

[max-sixty]

I hit this in #96.

I'm surprised this requires manually configuration, particularly since often the correct remote will be upstream while the fork will be origin. Is my experience different from others'?

The message is also very non-obvious (particularly since origin was a GH repo, even if it wasn't one that runs GH Actions):

Currently this is the only extension I need to configure for each project individually. A rule like "Try origin, if that doesn't work, try the other one" would catch most cases.

[qc00]

I was thinking of raising a separate enhancement ticket, but I now feel this is really a bug

[KetchupOnMyKetchup]

The PR has been completed and the fix will be available in our upcoming release v0.25.7, which planned for release May 5, 2023. Thanks so much for submitting great bugs and feedback to help make the extension even better!

[KetchupOnMyKetchup]

The fix has been released and is available in v0.25.7 🎉 !