Skip to content

Bug: Custom workflows default to workflows/default as the path when no path is specified breaking user expectations #1047

@jwforres

Description

@jwforres

When selecting a Custom Workflow if you leave the path empty then the launcher decides to look for your workflows under a workflows/default folder. This breaks common user expectations when specifying git repos and paths that an empty path means look in the root of the git repo. It is unlikely anyone was using the current behavior of workflows/default so we should fix the default of no path to use the repo root.

Metadata

Metadata

Assignees

No one assigned

    Labels

    amber:auto-fixAmber agent: automated low-risk fixes (formatting, linting)bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions