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

Pants

~Is there a page or part of the docs that describe what pre-commit or CI might look like for a "complete" build-and-test of a Pants monorepo?~

~I ask because obviously there's `fmt`, `lint`, `check`, `test`, but what about `validate`? or `update-build-files --check`?~

Edit: The 2.8 docs have me covered :tada:

Bonus points if there was a GitHub action, which not only acts as documentation but also allows the community to have drop-in pants support on CI.

You should have the doc site bookmarked. The search there is decent. Here is what we've got <https://www.pantsbuild.org/docs/using-pants-in-ci|https://www.pantsbuild.org/docs/using-pants-in-ci>

~Yeah that page certainly can be helpful, but I think the summary line sums it up well: "Suggestions for how to use Pants to speed up your CI"~

~Whereas it'd be nice to have a section about what a CI pipeline looks like.~

---

~I see now two links at the top. A broken `travis.yml` one, and a GHA one, but the GHA one doesn't mention `validate` or `update-build-files`~ :disappointed:

Oh wait, the 2.8 docs actually look more beefy: <https://www.pantsbuild.org/v2.8/docs/using-pants-in-ci>

Yeah, switching the "default" docs to 2.8 very soon