A collection of reusable GitHub Actions workflows for standardizing development processes across repositories.
Two workflows that work together to manage the release process:
Creates a release branch and prepares the changelog for release.
Trigger:
Push a tag with prefix prep-v
(e.g., prep-v1.0.0
)
Actions:
- Creates a release branch
- Moves Unreleased changelog items to a new version section
- Removes the Unreleased section for release
- Creates a PR for review
Usage:
git tag prep-v1.0.0
git push origin prep-v1.0.0
Automatically updates the changelog when PRs are merged to develop.
Trigger:
PR merged to develop branch
Actions:
- Adds PR to Unreleased section of changelog
- Creates Unreleased section if it doesn't exist
- Maintains changelog formatting
Usage: Automatic - no manual steps required. PR merges to develop trigger the workflow.
The workflows maintain the following changelog format:
# Repository Changelog
*Note: the changes in this log are automatically generated and commited via github actions, modify only if you know what you are doing!*
## **MM/DD/YYYY - Unreleased**
- PR #{number}: {title}
## **[(MM/DD/YYYY) - {version}](https://github.com/{org}/{repo}/releases/tag/{version})**
- PR #{number}: {title}
- Copy the desired workflow files to your repository's
.github/workflows/
directory - No additional configuration needed - workflows use repository context for variables
- GitHub repository with develop branch
- Permissions to push tags and create PRs
- Changelog.md file in repository root (will be created if missing)
- Create a feature branch off develop
- Make your changes
- Create a PR to develop
- Changelog will be automatically updated upon merge
For issues, questions, or contributions:
- Open an issue in this repository
- Include workflow name and description of need
MIT License - See LICENSE.md file for details