It took me longer to figure out how to use this action than I'd have liked, so here's a docs PR! I believe the minimal package.json example will work for most people writing node actions.
One thing that caught me out is that any actions using build-and-tag-action currently won't work on their main branch as using in action.yml is set to node12 but a compiled file does not exist in the repo.
npx convert-action rewrites the runs section in action.yml, allowing people to specify using: docker in their action.yml file on main (which enables people to use the bleeding edge if required) knowing that when npm run build is executed, runs will be changed to node12
It took me longer to figure out how to use this action than I'd have liked, so here's a docs PR! I believe the minimal
package.jsonexample will work for most people writingnodeactions.One thing that caught me out is that any actions using
build-and-tag-actioncurrently won't work on theirmainbranch asusinginaction.ymlis set tonode12but a compiled file does not exist in the repo.npx convert-actionrewrites therunssection inaction.yml, allowing people to specifyusing: dockerin theiraction.ymlfile onmain(which enables people to use the bleeding edge if required) knowing that whennpm run buildis executed,runswill be changed tonode12For an example of this working, see the actions run and resulting tag commit