Add backport setups as we now have 1.x branch. #53
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.
Signed-off-by: Peter Zhu [email protected]
Description
Add backport setups as we now have 1.x branch.
Since 2.0.0 is coming I would keep
main
as 2.x.x and create a new branch1.x
.The 1.x branch will serve as the active branch for 1.3.x and others in 1.x.
If anyone pushing code that runs on both
1.x
andmain
, they can just open PR tomain
then add the tagbackport 1.x
to the PR and the workflow will automatically create backport PR.If the code is specific to main branch and 2.x.x then they can ignore adding the tag.
Thanks.
Issues Resolved
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.