You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Report what staging branches a PR can land cleanly on #77
I reckon just trying to rebase any branch against whatever branch would be pretty cheap? These doesn't have to show up in regular PR's, just one's that has a the land-on-$foo stuff?
I reckon just trying to rebase any branch against whatever branch would be
pretty cheap? These doesn't have to show up in regular PR's, just one's
that has a the land-on-$foo stuff?
Why use the lts-watch-* labels? Shouldn't those be added by users whether there are merge conflicts or not?
Also, how would you know which labels should be added (which branches to test), unless you mean to try all branches that are not specifically excluded via do-not-land-on-* labels?
Another issue is how would you keep the labels up-to-date? If someone hasn't updated their PR/branch in awhile, there could be merge conflicts at some point.
If we stick with labels, maybe a new set of labels would be best? Like lands-cleanly-on-* or something?
Is it possible to have a webhook like Travis and other services that shows the information at the bottom of the PR? If so, would that be better than labels?
Activity
phillipj commentedon Sep 12, 2016
Huh, this sounds like a cool feature! Should it post a comment or add labels?
addaleax commentedon Sep 12, 2016
I think labels would be good? They are pretty cheap, and maybe it’s just me but I find automated github comments by bots more noisy than helpful.
jbergstroem commentedon Sep 12, 2016
I reckon just trying to rebase any branch against whatever branch would be pretty cheap? These doesn't have to show up in regular PR's, just one's that has a the land-on-$foo stuff?
MylesBorins commentedon Sep 13, 2016
what I would personally like to see would be automating adding the
Lts-watch labels if a commit lands cleanly on that release stream
On Tue, Sep 13, 2016, 1:16 AM Johan Bergström notifications@github.com
wrote:
jbergstroem commentedon Sep 13, 2016
Oh - that would be pretty neat.
mscdex commentedon Oct 18, 2016
Why use the
lts-watch-*labels? Shouldn't those be added by users whether there are merge conflicts or not?Also, how would you know which labels should be added (which branches to test), unless you mean to try all branches that are not specifically excluded via
do-not-land-on-*labels?Another issue is how would you keep the labels up-to-date? If someone hasn't updated their PR/branch in awhile, there could be merge conflicts at some point.
If we stick with labels, maybe a new set of labels would be best? Like
lands-cleanly-on-*or something?Is it possible to have a webhook like Travis and other services that shows the information at the bottom of the PR? If so, would that be better than labels?
scripts: new attempt-backport script for PRs
attempt-backport: only run PRs targeted at master
attempt-backport: use options.logger
attempt-backport: enable label removal for Current lines
attempt-backport: disable label removal for now
attempt-backport: fix lint
scripts: new attempt-backport script for PRs
attempt-backport: only run PRs targeted at master
attempt-backport: use options.logger
attempt-backport: enable label removal for Current lines
attempt-backport: disable label removal for now
attempt-backport: fix lint