Skip to content

Fix wildcard to include branch names with slashes #331

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 12, 2022

Conversation

greglittlefield-wf
Copy link
Collaborator

From the GitHub Actions docs:

The * wildcard matches any character, but does not match slash (/).

The ** wildcard matches any character including slash (/) in branch and tag names.

This PR updates to use ** instead of * so that GitHub Actions run on all branches, as opposed to skipping branches containing slashes.

@aviary3-wk
Copy link

Security Insights

(2) Vulnerable direct dependencies were detected
  • 1 vulns in ansi-regex < 5.0.1 via yarn.lock
  • 1 vulns in glob-parent < 5.1.2 via yarn.lock
  • Action Items


    Questions or Comments? Reach out on Slack: #support-infosec.

    Copy link
    Collaborator

    @sydneyjodon-wk sydneyjodon-wk left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    +10

    @Workiva/release-management-p

    Copy link

    @rmconsole-wf rmconsole-wf left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    +1 from RM

    @rmconsole6-wk rmconsole6-wk merged commit f622ef0 into master Jan 12, 2022
    @rmconsole6-wk rmconsole6-wk deleted the greglittlefield-wf-patch-2 branch January 12, 2022 15:51
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    6 participants