If pushurl has been set to prevent a remote from being pushable (which I tend to do in order to ensure I never ever push upstream, https://stackoverflow.com/a/10260389), then the extension is unable to find any info about the repo, workflows, secrets, etc.
To Reproduce
Steps to reproduce the behavior:
Check out a fork.
Add an upstream.
Set upstream to be unpushable using (git remote set-url --push upstream no_push)
Set "github-actions.remote-name": "upstream" in settings.json.
Expected behavior
The repo works as normal. After all, all of the other settings point to the right places:
Describe the bug
If
pushurl
has been set to prevent a remote from being pushable (which I tend to do in order to ensure I never ever push upstream, https://stackoverflow.com/a/10260389), then the extension is unable to find any info about the repo, workflows, secrets, etc.To Reproduce Steps to reproduce the behavior:
upstream
to be unpushable using (git remote set-url --push upstream no_push
)"github-actions.remote-name": "upstream"
insettings.json
.Expected behavior
The repo works as normal. After all, all of the other settings point to the right places:
Screenshots
With pushurl set:
With it unset:
Extension Version
v0.26.2