canonical / canonical/documentation-workflows
Separate composite actions are no longer necessary
- Dominant language
- Python
- Stars
- 5
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Ignoring the legacy woke and aspell installations (see https://github.com/canonical/documentation-workflows/issues/33 and https://github.com/canonical/documentation-workflows/issues/42), we currently have three composite actions for calling a user-provided make target.
I believe that we should dissolve the composite actions and incorporate them into the existing workflows, as they add an unnecessary layer to the call stack and require too much boilerplate to be useful outside of this repository.
We could have one composite action for calling the make target, but I don't think it would save enough effort to justify the added complexity.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.