Skip to content

E2E workflow has hardcoded path to dynamic repository name if run on dispatch #2457

@odockal

Description

@odockal

Bug description

If we change the repositoryName when the e2e workflow is run on demand (dispatch) the path to repository is still hardcoded:

      - name: Ensure getting current HEAD version of the test framework
        working-directory: ./extension-bootc/tests/playwright

and possible on other places of the https://github.com/podman-desktop/extension-bootc/blob/main/.github/workflows/e2e-main.yaml

Operating system

Any

Version

next (development version)

Steps to reproduce

run the workflow https://github.com/podman-desktop/extension-bootc/blob/main/.github/workflows/e2e-main.yaml with a custom organization, branch and repository name (ie. old one: podman-desktop-extension-bootc). The workflow will fail.

Relevant log output

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions