Instead of maintaining our common GitHub Workflows and Custom GitHub Actions in this repository, instead integrating this repository's workflow-templates/ folder with the separate repository: noclocks/ghactions as a git sub-module makes more sense and aids with separation of concerns between GitHub management and a separate actions repository.

• Create separate noclocks/ghactions repository using the noclocks/template-generic-repo template repository.
• Add Changelog Workflow to noclocks/ghactions
• Add MkDocs Publish Workflow to noclocks/ghactions

Reference

• Sharing workflows, secrets, and runners with your organization - GitHub Docs
• Sharing actions and workflows from your private repository - GitHub Docs
• Reusing workflows - GitHub Docs
• continuous integration - What is the most efficient way of sharing github workflows across several repositories? - Stack Overflow
• How to reuse scripts - Yaml import/require · Issue #245 · actions/starter-workflows
• Re-usable and maintainable GitHub Action workflows for multiple repositories - DEV Community
• Feature request: allow workflow configuration in sub-folders · community · Discussion #18055
• Reusable Github Action Workflows II: Integration Testing | by Başak Tuğçe Eskili | Marvelous MLOps | Medium
• Creating starter workflows for your organization - GitHub Docs
• About workflows - GitHub Docs
• How to share the Github Actions workflow in an organization privately | by Nitin Singh | Medium