Use meseeksdev for backporting

[TomAugspurger]

cc @jreback @jorisvandenbossche OK by you? Enable at https://github.com/apps/meeseeksdev/installations/new

I think @Carreau whitelisted the pandas org.

[jorisvandenbossche]

Just to understand the workflow here that would be used: Meeseeks will open a new PR for each PR that we tag for the bugfix release? (in constrast with the bulk cherry-picking that we now did more manually)

That gives some more traffic on github .. but on the other hand is also more transparent.

Anyhow, it's good to look at way to automate this more!

[Carreau]

So far it is based on milestone.
You edit your milestone description with commands to be executed on merge.

For example IPython 5.7 milestone contains:

on-merge: backport to 5.x
on-merge: backport to 6.x

So for example when ipython/ipython#11043 was merged in master, the PR ipython/ipython#11046 was automatically open.

If the bot can't cherry pick, it complains on the PR and tag it with "Still needs manual backport". for example : ipython/ipython#10707 (comment)

You could of course add

on-merge: say "Oweeeee"

Or any other command you like the bot understand. (tag, untag, say, ... )

You can also mention the bot and ask it to do things. If you have commit right on the repo (and the bot is enabled), the bot will respond.

It push the backported branch on the same repository, because of some GitHub limitation as you can't make cross-repo PRs with integrations tokens. I have plan to fix that by creating a machine-account, and juggling with tokens, but so far haven't found the time to do it.

Does that clarify things ?

[Carreau]

It push the backported branch on the same repository, because of some GitHub limitation as you can't make cross-repo PRs with integrations tokens. I have plan to fix that by creating a machine-account, and juggling with tokens, but so far haven't found the time to do it.

I've now implemented (in beta) the ability to backport without requiring push permissions. See scientific-python/MeeseeksDev#28

I'll switch the default mechanism after some testing, and then remove the request for push access.

[jorisvandenbossche]

@Carreau thanks for the explanation!

An additional question: it is also possible to have a command to say to the bot to still backport a PR once it is already merged? (eg in case you forgot to label it or only decide afterwards to still target it for that release, or now in our case because the bot was not yet enabled)

[TomAugspurger]

Should be @MeeseeksDev backport to 0.23.x.

[jorisvandenbossche]

Ideally I would like to have something that does backports in batches to avoid many PRs, but if this improves the workflow, let's go for it :)

[TomAugspurger]

I think I can manually backport this first batch, and then we'll start using the bot for new ones.

…

On Thu, Jun 7, 2018 at 8:38 AM, Joris Van den Bossche < ***@***.***> wrote: Ideally I would like to have something that does backports in batches to avoid many PRs, but if this improves the workflow, let's go for it :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21070 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQHIkIIiTKvpY4UxVKOTvTFKIwUGmXMks5t6SzLgaJpZM4UAjxW> .

[Carreau]

Ideally I would like to have something that does backports in batches to avoid many PRs, but if this improves the workflow, let's go for it :)

If you want to have something that avoids PRs and push directly to stables branches it is feasible. We just need to modify the command to directly push. Which should not be too hard.

[TomAugspurger]

@meeseeksdev Hello

[Carreau]

Hum... it may be case sensitive. Try lowercase ?

[jorisvandenbossche]

@meeseeksdev hello

[TomAugspurger]

FWIW, I think I requested permission for pandas-dev/pandas a couple days ago. Not sure if it went through.

[Carreau]

Hum, it did not receive any events from GitHub. Is it correctly activated ? I restarted the bot just in case.

[TomAugspurger]

Seems like it's still staging.

[Carreau]

Hum, that's not from my end, I should not have to validate any of these.

[Carreau]

An admin of the org maybe ?

[TomAugspurger]

@meeseeksdev Hello

[lumberbot-app]

I'm Mr. Meeseek, @TomAugspurger, Look at meee !

[mroeschke]

Looks like we've enabled this. Closing