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 branch 1.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 and main, they can just open PR to main then add the tag backport 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
[x] Commits are signed per the DCO using --signoff
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.
Signed-off-by: Peter Zhu zhujiaxi@amazon.com
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.