#18202 Prevent Pants from inserting lock file header with local machine binary path Issue created by rafrafek How can I prevent Pants from inserting this into the lock file?

// This lockfile was autogenerated by Pants. To regenerate, run:
//
//    /Users/my_user_name/Projects/my_project_name/scie-pants-macos-aarch64 generate-lockfiles --resolve=python-default
//
// --- BEGIN PANTS LOCKFILE METADATA: DO NOT EDIT OR REMOVE ---

I want the lock file to be the same no matter which machine created it. And I don't want to store my local machine paths in git repo. I've tried with:

./scie-pants-macos-aarch64 generate-lockfiles --generate-lockfiles-custom-command=./pants

But it will create instruction that is not valid:

// This lockfile was autogenerated by Pants. To regenerate, run:
//
//    ./pants
//
// --- BEGIN PANTS LOCKFILE METADATA: DO NOT EDIT OR REMOVE ---

Trying to fix it using

--generate-lockfiles-custom-command

would lead to something like

--generate-lockfiles-custom-command="./pants generate-lockfiles --generate-lockfiles-custom-command='recursion here?'"

pantsbuild/pants

#18202 Prevent Pants from inserting lock file header with local machine binary path Issue closed as completed by rafrafek pantsbuild/pants