Skip to content

glob syntax is not intuitive, readme not specific enough #284

@Gornoka

Description

@Gornoka

In my opinion the readme does not specify clearly enough how globs should be specified, especially when they start with a wildcard.

My problem was that " like it is used in the workflow definition yields to blobs being not recognized.

A comment in the readme , that using " (like in the action for branch filtering) instead of ' will crash the action would be very nice to have.
A comment that leading wildcards without " or ' will crash the action would be nice to have.
Kind regards
Lukas

update: when testing more i found out that apparently sometimes " work, but i have no idea why they did not at other times.
the only thing that i have found that consistently does not work is blank globs without either ' or " and wildcards at the beginning.

#works
python:
- '**/*.py'
# crashes
# python:
# - **/*.py
# works
python:
- "**/*.py"

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions