Skip to content

Setting upstream pushurl to a bad value to prevent pushing prevents branch from being used to find Actions info #298

@jakebailey

Description

@jakebailey

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:

  1. Check out a fork.
  2. Add an upstream.
  3. Set upstream to be unpushable using (git remote set-url --push upstream no_push)
  4. 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:

[remote "upstream"]
        url = git@github.com:microsoft/TypeScript.git
        fetch = +refs/heads/*:refs/remotes/upstream/*
        gh-resolved = base
        pushurl = no_push

Screenshots

With pushurl set:

image

image

With it unset:

image

image

Extension Version
v0.26.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    Status

    Backlog 🗒

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions