Doesn't work with manual trigger (workflow_dispatch) #146
Comments
|
Hi there - you need a first step of |
|
Thanks, but that just changed the error. I trid both your suggestion Full log: |
|
Hmmm okay so how are you triggering this run? I see |
|
I don't know of any other way to do it, Since this tag is the current version that the WordPress.org people accepted I don't want to bump version numbers just to run this Action. I'd prefer to only have it happen manually and remove the |
|
FWIW I still use SVN directly for some things and it's fine, much like Actions it's a tool to learn if you're going to use it. In any case, I'm not really sure what your expectations are for the tag name given that it will deploy live - the stable tag is defined in |
|
Thanks again but I'm afraid I just don't understand these concepts. Why can't this Action run manually? The errors seem to indicate a non-existent folder is being accessed. I have a tag on my latest release, why is that not picked up rather than requiring a new tag to trigger the Action? I'm sorry for wasting your time, there must be something going on like you said where this action just doesn't work manually. And I don't want automated, I only want manual. |
|
This Action is built to be automated, I haven't tested it myself but I think you could make it work manually by requiring an input for the version which you would then pass to the workflow for the Adding that input is going to be a lot more work than you creating a tag in the GitHub interface named |
|
I appreciate the explanation and your quick responses. The fact that there's no easy way to add a tag to trigger an Action without creating a fake release that you later delete means I haven't tried that. I tried following a tutorial for TortoiseSVN but it didn't work. This is just too much hassle to be on the WordPress.org repository so even though I am approved I guess no one will ever be able to use it because I can't get the files onto site. |
clubside
changed the title
|
I think it would help to understand what you are trying to do and how you expect this work long-term (will you always manually trigger it, how is that different from creating the tag in Git/GitHub, etc.). There is a |
|
I can confirm that the action does work with 
As @helen said above, the deploy script attempts to parse out the tag's version from the ref which is what is selected above when doing a manual run, but it will always default to the default branch which is why it's failing for you. |
Howdy!
I just had my plugin approved and had set things up ahead of time to take advantage of your action. Now that the time is here it doesn't work. Nor do any of the forks. It all seems to be tied into the fact that my plugin is very simple: a single
PHPfile andreadme.txt.I originally used a
.distignorefile but have add a.gitattributesas well. Both fail I suppose, the debug information like the documentation around GitHub Actions is obtuse.My plugin: https://github.com/clubside/vern-responsive-video
My action file:
Most recent failure:
I have no idea how the "not a git repository" message is even possible given...it is?
Any help greatly appreciated, I hate to have to learn and use SVN for this tiny project.
Thanks,
Chris
The text was updated successfully, but these errors were encountered: