Add create release branch workflow #1248
Open
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
austinvazquez
force-pushed
the
add-create-release-branch-automation
branch
3 times, most recently
from
cbbe038
to
e8d203d
Compare
austinvazquez
force-pushed
the
add-create-release-branch-automation
branch
11 times, most recently
from
d5bdda5
to
a82d775
Compare
austinvazquez
force-pushed
the
add-create-release-branch-automation
branch
2 times, most recently
from
1f10ddd
to
1b6a6c1
Compare
austinvazquez
added
the
github_actions
This change adds a GitHub Actions workflow for creating release branches with jobs to 1) create the branch and 2) open a pull request with the generated THIRD_PARTY_LICENSES file and updated getting started guide version. Signed-off-by: Austin Vazquez <[email protected]>
austinvazquez
force-pushed
the
add-create-release-branch-automation
branch
from
1b6a6c1
to
916aae9
Compare
pendo324
approved these changes
Aug 27, 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.
Issue #, if available:
Follow-up to #1238
On each release, there is a manual set of steps to generate the
THIRD_PARTY_LICENSESfile and set the version in the getting start guide on the new release branch. It would be nice to have some automation for creating the release branch and generating the changes needed so maintainers only have to approve and merge a single pull request.Description of changes:
This change adds a GitHub Actions workflow for creating a release branch and generating the pull request with the changes needed for
THIRD_PARTY_LICENSESfile and updating the getting started guide.Testing performed:
Merged workflow to fork and ran to create
release/v0.8branch.Ran via command like:
GitHub Action workflow run - https://github.com/austinvazquez/soci-snapshotter/actions/runs/9334082659
PR for adding
THIRD_PARTY_LICENSESand updating getting started guide - austinvazquez#40Alternatives considered:
Limitations:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.