Update release.yml #736
Merged
Update release.yml #736
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
philipwindecker
added
Documentation
pmai
force-pushed
the
philipwindecker-patch-1
branch
from
5cc0299 to
aa29f4f
Compare
Added Antora Generator call at the end to trigger the GitHub Pages build. Signed-off-by: Pierre R. Mai <pmai@pmsf.de>
pmai
force-pushed
the
philipwindecker-patch-1
branch
from
aa29f4f to
ef55b4d
Compare
pmai
approved these changes
Nov 6, 2023
pmai
added
ReadyToMerge
Contributor
|
Reviewed for v3.7.0 |
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.
Added Antora Generator call at the end to trigger the GitHub Pages build.
Add a description
When a release is published, the release pipeline generates the new release package.
However, currently the Antora Generator only runs in that pipeline to create the slimmer package output.
The GitHub pages are, therefore, not updated with the new release automatically.
To solve this, a final call was added to trigger the Generator after the package has been created and uploaded. This will ensure that the new tag is also included in the GitHub pages, but only if the release update was successful.