Matt
@rkit this can be closed.
@xrep, can you please create a jsfiddle of your issue?
If I remember correctly it also has to do with permissions, your regular `github.token` has read only permissions, you need to setup a `REPO_ACCESS_TOKEN` which has write permissions for an...
When trying to target a specific release you need to include the full name, in this case `v1.4.0` is what you need there. However @spacewaterbear is correct, by including `master`...
Just had this crop up on me as well. Not sure what changed? I believe my primary setup is working fine but I copy/pasted the command to another workflow and...
Verified another one of my branch workflows is also broken.
I don't think this is the case, I'm using the `sha` on multiple workflow triggers and it works just fine. I'm actually running into the same issue with `ref` so...
Following up here, any plan to address this?
Hey @saliceti I am on a branch, trying this as part of my **PR verification** to use the same `test` config as my **Release** workflow. My understanding from GitHub is...
Still an issue :(