Skip to content

README.md

Latest commit

 

History

History
38 lines (27 loc) · 1.9 KB

README.md

File metadata and controls

38 lines (27 loc) · 1.9 KB

github-release-workflow

Important

To ensure changelogs are generated correctly, all git commit messages must follow the Conventional Commits specification.

Also, you must go to your repository Settings > Actions > General > Workflow permissions and enable "Allow GitHub Actions to create and approve pull requests", otherwise the automated release process will fail.

🚀 Instant Magic for Your Repository!!!

Add professional release automation to your personal project with a single step:

Copy the prepare-release.yml and publish-release.yml files from .github/workflows into your project's .github/workflows directory.

✨ That's it! Your repository is now enchanted.

⚙ How It Works

This workflow streamlines your release process into a few simple steps:

  1. Tag Your Release: On your development branch (separate from master or main), create a git tag with a v prefix (e.g., v1.0.0).

    git tag v1.0.0

  2. Push the Tag: Push the tag to GitHub.

    git push origin v1.0.0

  3. Automated Magic: GitHub Actions will automatically:

    • Generate a changelog based on your conventional commits.
    • Create a specific release branch.
    • Open a Pull Request to your default branch (e.g., master).

  4. Review and Merge: Review the Pull Request created by the bot.

    • Do not modify the Pull Request title or body, as they are used for the release metadata.
    • Merge the Pull Request.
    • The workflow will automatically create a GitHub Release for you.