Automating PR backports

Hi everyone,

I’m working on getting our development workflow automated by working on low hanging fruit.

I started with warning about direct pushes to master/release branches, but I’d like to add automation for backporting things to stable as well.

backport action looks really promising, but we’d have to rename needs: port to stable label to include branch name, so something like needs: backport to release-20.09 and needs: backport to release-21.05, etc.

Would that break any other automation or use cases?

13 Likes
4 Likes