feat: update releases when release branches change #26
Conversation
This file contains 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
This change enables automatic PDF generation for releases when release
branches are changed. This supports "backporting" changes to prior
releases.
This works by:
- Creating a branch named 'release/XYZ', where XYZ is the name of a
release, when a release is made.
- Activating PDF generation when 'release/XYZ' branches are changed.
- Updating the release XYZ when PDF generation is finished.
The release may be named anything. The only portion of the name that is
important for these actions is 'release/' in the branch name.
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.
This change enables automatic PDF generation for releases when release
branches are changed. This supports backporting changes to prior
releases.
This works by:
release/XYZ, where XYZ is the name of arelease, when a release is made.
release/XYZbranches are changed.The release may be named anything. The only portion of the name that is
important for these actions is
release/in the branch name.The generated PDFs will be accessible from the Release pages and the links
to these PDFs are stable.
No manual work needs to be done beyond creating a release. All other steps
should happen automatically as normal development happens.