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

Pants

<@U0N6C2Q9F>: so, currently `./pants experimental-bsp` creates both `.bsp/pants.json` and `.pants.d/bsp/scripts/run-bsp.sh` … but an issue is that new users won’t have a `.pants.d/bsp` directory

```        bsp_dir = build_root.pathlib_path / ".pants.d" / "bsp"

        bsp_scripts_dir = bsp_dir / "scripts"
        bsp_scripts_dir.mkdir(exist_ok=True, parents=True)

        bsp_logs_dir = bsp_dir / "logs"
        bsp_logs_dir.mkdir(exist_ok=True, parents=True)```

`parents=True` should handle making all parent dirs, right?

two options i see:
1. don’t recommend committing the `.bsp` directory, and instead suggest that every user run `./pants experimental-bsp` the first time they want to use IJ
2. do recommend committing the `.bsp` directory, but ignore the script within it

(1) is what I was thinking when writing the code

yea, it seems like 1. might be the way to go. because i think that we’ll need individual users to run a CLI command to actually select the “group” to load too, so they’ll already need to run it.