add new workflow to generate release info html files #418
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
test-fullautomation
added
0.13.1
documentation
test-fullautomation
approved these changes
Dec 9, 2024
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.
Hi Thomas,
This PR add new Github workflow for generating the release_info html files.
This workflow can be triggered manually or automatically by any change in
tools/release_info/release_main_info_*.jsonfiles.The release info html files is stored job artifact, so that you can quickly review your changes.
I am working with the appropriate job(s) for internal build infrastructure.
As soon as the internal job is added, I will split the
main_release_infofile into 2 versions for BIOS and OSS.Thank you,
Ngoan