cloudfoundry / loggregator-release

Cloud Native Logging

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Branch matching in github actions isn't working

ctlong opened this issue · comments

I noticed that a PR to v106.3.x didn't trigger the unit-tests action.

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

Possibly the branches need to be string-ified (see here). So

    - v105.6.x
    - v106.3.x

becomes

    - 'v105.6.x'
    - 'v106.3.x'

The above idea did not work.. I found a comment on a support thread that indicated that we would need to push workflows to every branch.