-
Notifications
You must be signed in to change notification settings - Fork 39
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
Branches with slash (/
) in their name are not supporten in GitHub Actions
#422
Comments
1 task
tomalec
added a commit
to woocommerce/google-listings-and-ads
that referenced
this issue
Jul 7, 2021
tomalec
added a commit
to woocommerce/google-listings-and-ads
that referenced
this issue
Jul 7, 2021
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Report a bug.
What is the current behavior?
When I run bundlewatch in a GitHub action on a branch that contains a
/
it fails to recognize it and cuts it after the first slash (fix/issue/123-slashes-in-branch
).If the current behavior is a bug, please provide the steps to reproduce.
fix/issue/123-slashes-in-branch
What is the expected behavior?
All branch names are supported.
If this is a feature request, what is motivation or use case for changing the behavior?
n/a
Please mention other relevant information such as the browser version, Node.js version, bundlewatch version, and Operating System.
I'm using latest bundlewatch
0.3.2
.I bet, the reason for this bug, is the bug in
ci-env
https://github.com/siddharthkp/ci-env/blob/master/index.js#L122 reading only the part between the second and third slash.Fix seems to be waiting at siddharthkp/ci-env#43
The text was updated successfully, but these errors were encountered: