Automating Managing LTS branches about automation HOT 6 CLOSED

@joyeecheung yup. We could definitely do that to flag the commits. We would need a bot that could poll for labels, land the commits, and push upstream.

TBQH at that point the landing of the commit isn't the biggest deal... it is more about the review of what should / shouldn't land. Although in thinking about it, if the process of landing the commit was abstracted from the review process it would likely be easier to onboard more reviewers, and potentially inspire folks to review their own PRs.

We would likely still need to audit the backlog of un labelled issues... but perhaps it would be easier to inspire people to label if it were an automated process...

from automation.

So, I've used https://github.com/evanlucas/node-backport for the past few releases I've done, and it sure makes things easier. Warning: It's pretty raw at this point though.

from automation.

IIUC correctly, right now we just backport every PR that has suitable semver labels? Or do lts-watch-x labels do the job?

from automation.

@joyeecheung currently I use branch diff to generate a list of commits with a command line

branch-diff v6.x-staging upstream/v8.x --exclude-label semver-major,semver-minor,dont-land-on-v6.x,backport-requested-v6.x,backported-to-v6.x,baking-for-lts --filter-release

and then manually review every commit. The labels are all manual too 😅

from automation.

@MylesBorins OK I think I get what you meant now, including certain labels instead of excluding? Yes right now that looks like too much manual pings.

from automation.

We've already done lots of related work in the github bot, trying to backport PRs and add different labels: nodejs/github-bot/scripts/attempt-backport.js.

Initially it also added dont-land-on-* labels which got disabled after lots of discussions (nodejs/github-bot/acd5bc).

I assume it something similar you're suggesting @MylesBorins with the addition of actually pushing changes to git branches?

from automation.