configurable directory for branch lockfiles

[nhomble]

Contribution

• I'd be willing to implement this feature (contributing guide)

Describe the user story

I am interested in branch lockfiles (this is related to other github issues I have participated in regarding frequent git conflicts).

I am looking at branch lockfiles, and one sour point from strictly a UX perspective is the amount of clutter at the root of the repo. I don't want to change any functionality but also I want to avoid the root of my repo having all of this noise.

Describe the solution you'd like

I propose a new configuration property (defaulted to project root) in the pnpm-workspace that would let teams commit their branch lockfiles in a different directory.

Describe the drawbacks of your solution

Typically lockfiles are at the root of the repo, so this may be surprising to people entering a project configured this way for the first time. But then again, having a lockfile per branch isn't something people who are used to plain npm projects would be used to anyway.

Describe alternatives you've considered

I considered just updating the file name to be hidden (.pnpm-lock.<branch>.yaml) but allowing for a custom directory seems like the same amount of work with a lot more extensibility.