Skip to content

uses: with fully qualified URLs raises two errors per use #559

@CaramelConnoisseur

Description

@CaramelConnoisseur

Describe the bug
When using actions hosted off GitHub, e.g. on internal git servers, using the full repo URL (e.g. https://git.example.com/example/example-action@v1) the add on tries to make it a GitHub URL (https://github.com/https/git.example.com/example/example-action@v1) and subsequently reports:

  • Unable to resolve action 'https://git.example.com/example/example-action@v1', repository or version not found
  • Expected format {owner}/{repo}[/path]@{ref}. Actual 'https://git.example.com/example/example-action@v1'

To Reproduce
Steps to reproduce the behavior:

  1. Upload an action to any non-GitHub repo service, e.g. an on-prem Gitea instnace.
  2. Create a workflow in VS Code using that workflow, e.g. uses: https://git.example.com/example/example-action@v1
  3. See error

Expected behavior
The uses value should be recognised as a fully-qualified URL and the action should be queried from there rather than rewriting it to a GitHub URL.

Screenshots
N/A

Extension Version
v0.30.0

Additional context
N/A

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