Backport and milestone #23
Comments
|
by auto-backport you mean behavior where users don't tell meeseeks to do anything? As soon as a PR is merged it automatically backports to other branches? |
|
Yes Basically if a PR is merged on master and has a milestone, MrMeeseeks will trigger the commands present in the Milestone Description. It's actually implemented, I changed a a bit the way it work. And mr meeseeks would backport on the branch v2.1.x and say "Oh Weeeee" For example https://github.com/MeeseeksBox/test1/milestones |
|
very interesting! I like it
--
…On Wed, Oct 4, 2017 at 10:23 AM Matthias Bussonnier < ***@***.***> wrote:
Yes
Basically if a PR is merged *on master* and has a milestone, MrMeeseeks
will trigger the commands present in the Milestone Description.
It's actually implemented, I changed a a bit the way it work.
In the milestone description you can put lines that say:
on-merge: backport to v2.1.x
on-merge: say "Oh Weeeee"
And mr meeseeks would backport on the branch v2.1.x and say "Oh Weeeee"
For example https://github.com/MeeseeksBox/test1/milestones
even if "say" is not implemented yet.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABwSHRefpxOskZdbSWOFAR56RcMYBmktks5so78XgaJpZM4PjRor>
.
|
|
@meeseeksdev say Oh Weee !!! |
|
O h W e e e ! ! ! |
|
@meeseeksdev say Oooooooohhhhh yeeeahh |
|
retry ? You can use say only if you have write permission. |
|
@meeseeksdev say Oooooohhhh yeahhh! |
|
Oooooohhhh yeahhh! |
|
😍 |
|
@meeseeksdev say 💯 |
|
💯 |
|
hehe I think that confused it |
|
@meeseeksdev say 😍 |
|
😍 |
|
@meeseeksdev say 🔢 |
|
🔢 |
|
@meeseeksdev say @meeseeksdev say oooohhhhhhhh |
|
oooohhhhhhhh |
|
damn! |
|
Y'all are making for a hilarious e-mail feed. 😜 |
|
lol mr meeseeks is going to cause so much more github noise |
|
what do you think mr meeseeks? @meeseeksdev say suuuuure thing chris! |
|
suuuuure thing chris! |
|
I'm considering allowing command in html comments to hide them :-) |
|
Testing... |
|
Oh Yeah that works ! |
|
cool! |
|
ooooohhhhhh weeee, who told me to say this? oh jeez I don't know! |
|
@choldgraf please stop |
|
Yeah Chris shut up. |
|
lol you messed up your HTML hiding ;-) |
|
yeah matthias, you need to add the ! in there 😝 |
|
yeah matthias, you need to add the ! in there |
@choldgraf and @tacaswell, about auto backport:
What about a mini-language in milestone description, something in the milestone description(editable on GitHub) that tell the bots which branches to backport to; Something like:
Allowing potentially multiple
- backport:targets.Thoughts ?
The text was updated successfully, but these errors were encountered: