💡 Would have sense to have file content in real files instead of strings?

[oscard0m]

An idea came to my mind from this PR: https://github.com/octoherd/create-octoherd-script/pull/10/files

What if we have had this GitHub workflow as a file and checked periodically by renovate? An automatic PR would have updated it for us (and for future releases of actions we decide to us in workflows).

Checking other files we scaffold with https://github.com/octoherd/create-octoherd-script maybe some checks and logic could be applied:

• Prettier / Lint
• Unit tests / transpilation / compilation...
• Easier to manipulate with octoherd actions (modify its content in a programmatic way maybe?)
• It would open the door of scaffolding a package.json and package.lock with controlled version of packages (controlled by renovate) instead of doing an npm i (not sure if this is valuable or it complicates more the ecosystem)

What's your opinion here @gr2m

[gr2m]

What if we have had this GitHub workflow as a file and checked periodically by renovate? An automatic PR would have updated it for us (and for future releases of actions we decide to us in workflows).

That's a good idea, I think we can do that.

Checking other files we scaffold with https://github.com/octoherd/create-octoherd-script maybe some checks and logic could be applied:

I don't want to force too much setup on people, they have their own preferences. Right now I think we should should probably sit back and see what people using it say about it

[github-actions]

🎉 This issue has been resolved in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀