I'm doing a big batch of cherry picking of bug fix...
# development
b
I'm doing a big batch of cherry picking of bug fixes that landed on
main
between 2.18.0a0 and now, since 2.18.x branch was only created recently and so some of them were, e.g. cherry picked to 2.17.x but 2.18.x didn't exist at the time. Sorry for the noise!
b
How do I know if I missed the cut on my PRs
b
I looked over https://github.com/pantsbuild/pants/compare/2.18.x...main I've cherry picked a bunch of yours too
b
How did this happen? Did the milestone not exist until after the branch?
b
I think the milestone (and branch) were only created today, from the 2.18.0a0 tag
b
Oh, yeah that's a problem in the release process then
FYI @witty-crayon-22786 @happy-kitchen-89482 we may want to tweak that
w
I started that release, but didn't finish it, because you were taking it over: sorry about that. I noticed today that neither the branch nor the milestone had been created
b
Oh sorry, I meant I was gonna fix the broken release. Anywho, now we know and all I see is an opportunity for more automation 😈
b
(Looks https://github.com/pantsbuild/pants/pull/19632 was the only one of the dozens of PRs I cherry picked that didn't cherry pick cleanly. Could you take a look @bitter-ability-32190?)
b
Probably a timing issue?
Oh: https://github.com/pantsbuild/pants/actions/runs/6027517064/job/16352890479#step:3:35 So GitHub workflows, by default, won't push to a branch if the change contains a workflow yaml. Huh
I think the solution is to have the
checkout
use the WorkerPants PAT