path.Match does not match e.g. feature/foo when the pattern is just *. If users want to match strings with slashes, they must specify the pattern */* as well. For example, to match all branches, one must write branches: ["*", "*/*"]. This could trip up users who might expect * to match everything (as I just did).

Should we special-case "*" to be a catch-all? Or change the whole matching behaviour? Or leave as is?

This was detected as part of #690, which does nothing about it except calling it out in the docs.