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

Pants

question for the room: how are you integrating Pants (formatters and linters) with your git-hooks, if any?

the pantsbuild repo runs approximately `./pants --changed-since=HEAD typecheck lint`… downside of course is that if it fails you need to run `./pants fmt` manually. but interested in whether folks have different strategies!

Adding adjacent question <https://twitter.com/cczona/status/1375249373790015491|https://twitter.com/cczona/status/1375249373790015491>

```#!/usr/bin/env bash

# NB: pre-commit runs in the context of GIT_WORK_TREE, ie: pwd == REPO_ROOT

changed=("$(./pants --changed-fast --changed-parent=HEAD list)")

./pants fmt ${changed}```

I have this pre-commit hook locally
``` /bin/bash
./pants lint --changed-since=HEAD || exit 1```
I added these aliases to my bashrc
```alias fmt='./pants --changed-since=master fmt'
alias lint='./pants --changed-since=master lint'```


interesting! so <@U01EWU0TPTN>: you folks just auto-format in the hook

if people are expecting it, that’s about as easy as it gets

i’ve always been scared that folks would lose work. but if they’re expecting it / have editor buffers

Hum the formating never prvents you from commiting

I would say for us we would add the lint in the CI