Use of patchback bot

[felixfontein]

How about installing the patchback bot for this repository? This allows easier backporting of PRs - simply add the backport label for the corresponding stable-2.x branch, and the bot will create a backport PR (assuming no conflict happens).

In the collections I maintain, and in particular in community.general, this is really helpful and simplifies the backporting work a lot. For example I added the backport-6 and backport-7 labels to ansible-collections/community.general#6774, and on merge the bot created two backport PRs ansible-collections/community.general#6817 and ansible-collections/community.general#6818.

[oraNod]

@felixfontein This sounds good to me. @samccann is on PTO this week and this changes her process for doing backports so I'd like to give her time to voice any concerns.

In any case you should have sufficient access to the repo now to install the bot. If @samccann is cool with it maybe you could set things up and do a quick demo at the DaWGs? It sounds like the kind of thing we need to make life easier.

[felixfontein]

Let's discuss it once Sandra is back!

I created a PR (#50) with a (possible) patchback config for this repo, and also added the other steps necessary in its description.

[samccann]

Yes please! Would love something that got me out of the manual backporting role. Let's give it a try!

[felixfontein]

1. Add patchback config #50 is merged
2. I requested access for the bot to this repo (https://github.com/apps/patchback/installations/13041763)
3. I created labels backport-2.13, backport-2.14, backport-2.13 (https://github.com/ansible/ansible-documentation/labels)

As soon as the bot has been enabled for the repo, you can add one (or multiple) of these labels for a PR on devel, and the bot will automatically create a backport for that PR to the corresponding stable-2.x branch (assuming there are no conflicts).

[gotmax23]

We've enabled and configured the bot and have started using it.