From Alexander Kanavin,
Here's a cool CI feature I haven't seen until now: a backport bot. To use it, add labels to the pull request to master/main/trunk ("needs backport", "stable-branch-a", "stable-branch-b", etc), and the boot will create the pull requests into those branches by cherry-picking commits from main once they land there. Or if it fails to cherry-pick, then it will create the pull requests and ask for manual backports.
Every CI system (gitlab, github, what have you) should have this feature out of the box to be honest. Managing the flow of backports is a major headache for both submitters and maintainers when there's no tooling for it.
(before you ask, 'master branch first' is the only sane and sustainable branch policy, end of discussion)
https://lnkd.in/dCdGYE4c
hashtag#ci hashtag#git hashtag#configurationmanagement hashtag#branchmanagement
From Alexander Kanavin,
Here's a cool CI feature I haven't seen until now: a backport bot. To use it, add labels to the pull request to master/main/trunk ("needs backport", "stable-branch-a", "stable-branch-b", etc), and the boot will create the pull requests into those branches by cherry-picking commits from main once they land there. Or if it fails to cherry-pick, then it will create the pull requests and ask for manual backports.
Every CI system (gitlab, github, what have you) should have this feature out of the box to be honest. Managing the flow of backports is a major headache for both submitters and maintainers when there's no tooling for it.
(before you ask, 'master branch first' is the only sane and sustainable branch policy, end of discussion)
https://lnkd.in/dCdGYE4c
hashtag#ci hashtag#git hashtag#configurationmanagement hashtag#branchmanagement