[#47] Push release to Readme.com changelog#48
Open
swlodarski-sumoheavy wants to merge 2 commits intobitpay:2.1.xfrom
Open
[#47] Push release to Readme.com changelog#48swlodarski-sumoheavy wants to merge 2 commits intobitpay:2.1.xfrom
swlodarski-sumoheavy wants to merge 2 commits intobitpay:2.1.xfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR introduces a comprehensive GitHub Actions workflow that automates the entire release process for the BitPay Utils cryptography pack, eliminating manual steps and reducing the risk of human error.
Features
🚀 Manual Trigger with Inputs
The workflow is manually triggered via
workflow_dispatchwith three required inputs:master)9.3.3)📦 Automated Version Management
🏷️ Git Tagging
📝 Smart Changelog Generation
📚 ReadMe.io Integration
README_API_KEYsecretBenefits
Prerequisites
Requires the following GitHub secret to be configured:
README_API_KEY- Authentication token for ReadMe.io APITesting
This workflow can be tested by triggering it manually from the Actions tab with appropriate version and branch inputs.