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

Pants

Since the length of a goal name came up the other day, is there background on why it's `generate-lockfiles` instead of something like `lock`?

because we would like to remove it entirely via <https://github.com/pantsbuild/pants/issues/12014> !

`npm`, `cargo`, etc automatically rewrite the lockfile if inputs have changed, unless you have asked them to fail instead… and that’s what we’re aiming for

oh yeah. I remember this being annoying when I was first checking out bazel where it couldn't regenerate our lockfile even though it already knew about the upstream source/had the tools capable of generating it.

heh. unlike bazel, we _do_ already support manipulating files within a run (for `fmt`, etc)… so it’s mostly just about not needing every single `goal` to be aware of the fact that a lockfile might change during a run

None of the above motivates the longer name imo. The history being there where more than one lockfile related goal initially, if memory serves. 

that's right, I agree we should shorten to `lock`. That's a 2 line change -- we have infrastructure for deprecating a goal name

<https://github.com/pantsbuild/pants/issues/15568>