Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U051221NF>: thanks for getting the M1 workflow in place: sorry i missed review.

is there a reason that it is a separate workflow, rather than a job in the existing workflow?

it looks like that means it can’t depend on the `check_labels` job the way <https://github.com/pantsbuild/pants/pull/14935> did for other bootstrap jobs

Not a strong reason. It started out that way when I wasn't sure if we'd want to trigger it on a different set of builds than the existing workflow, due to resource contention on the single M1 machine, and to avoid confusion