I did create a a couple of simple actions which abstract this a little, but I agree it is best when everything is in the repository and self-contained.
So I have a "run tests" action which just executes .github/run-tests, and it is up to the project-owner to write "make test" in that script, or whatever else they prefer.
It keeps things well-defined, and portable, but avoids the need to have project-specific workflows. I like being able to keep the same .yaml files in all my projects.
So I have a "run tests" action which just executes .github/run-tests, and it is up to the project-owner to write "make test" in that script, or whatever else they prefer.
It keeps things well-defined, and portable, but avoids the need to have project-specific workflows. I like being able to keep the same .yaml files in all my projects.
https://github.com/skx/github-action-tester
Similar thing for building and uploading artifacts, run ".github/build" and specify the glob-pattern for your artifacts:
https://github.com/skx/github-action-build