Hugo van Kemenade

> No output from after executing `cherry_picker --continue`? I didn't actually do that step, I let the original PR author resolve it :) But trying again I get: 

> `click.style` supports only a limited number of colors by names (red, black, etc). I'm certainly no color whiz and realize some people who are red/green color blind might not...

It would be good to figure out some good defaults, as I'm guessing most won't want to fine tune the options. The colour names supported by Click: https://click.palletsprojects.com/en/8.1.x/api/#click.style

See the CI failures: we can't use the `match` statement (new in 3.10) because we support Python 3.8+. I'm also not sure if we need to expose `--bright` and `--dim`...

Are you using Git worktrees? Maybe it doesn't know how to checkout branches already checked out in other directories. If so, does it work when you cd to the 3.12...

I suggest we remove the "You're not inside a cpython repo right now! 🙅" handling and let the original exception and message bubble up and be displayed.

> It might be better to move this to python/bedevere, since he is the one performing checks related to the `skip-*` labels. At the sprint we talked about replacing some...

(Converting to draft whilst awaiting migration.)

Yes, there could be a build job that then uploads the build artifact using https://github.com/actions/upload-artifact and then two dependant jobs that use https://github.com/actions/download-artifact to fetch it and do their respective...

(See also https://github.com/python/core-workflow/issues/459.)