Template to create a new composite action, with some supporting self-describing release scripts.
Updates to action.yml update README.md based on the input and output description.
By default, the action has a step to check if this reference is being referenced by commit hash rather than tag or branch - and raises a warning if not.
An extra version property in action.yml expects a semver. This is used to create releases when the version is updated.
The templating process is based on the general approach of simonw/python-lib, but with a different default structure.
A new repository based on this template can be created in Github or through cookiecutter.
The templating process can be run entirely in GitHub to create a new repository.
Start here: https://github.com/ajparsons/composite-action-auto-template/generate
Add a one-line description of your repository, then click "Create repository from template".
This repo can also be used to set up a template offline using cookiecutter. To start the processs:
python -m cookiecutter https://github.com/ajparsons/composite-action-auto-template/
If you want to modify or extend this approach - the self-bootstrapping behaviour will only happen when a repo does not end in '-auto-template'. If you clone this repo, into a different user or org space, it will not self-bootstrap because the name is the same.
For example, if you wanted to extend this into a basic django template - you might fork or clone the repo and call it 'django-auto-template'. This will not self-bootstrap, but new projects created from that template would.
This project defines several meta tests in tests/ that will:
- Attempt to provision a template with basic variables.
This requires the packages listed in requirements.dev.txt to be installed.