Is there an option that controls whether Pants resolves the path of bootstrap script in suggestions? Sometimes it seems to be putting this in stuff I commit in things it generates (like lockfiles), and I don't really want my local repo path being committed to code... example:

// This lockfile was autogenerated by Pants. To regenerate, run:
//
//    /home/jreed/devel/aiven/aiven-core/pants generate-lockfiles --resolve=pylint

I'd rather it just say

./pants

tbh. Is that possible?

You can use

--custom-command

to change it

Thanks. That documentation seems to suggest that the default should be

./pants

though:

If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running

./pants generate-lockfiles --resolve=<name>

like normal.

That's not quite how I interpret that

I don't think anyone would complain if you fixed the default to be

./pants

like the docs say @flat-zoo-31952

Is there an issue? If not I'll create one. And I can take a look at that yeah. It does this for auto-suggestion too, when you run the wrong command, I think it's probably the same underlying library that's doing this, but I'd have to dig deeper to know for sure

No clue, your search is as good as mine there.

Yeah that seems like a bug, not what we actually want

yummy yummy more bugs in my tummy

I think some shells set the process name differently, so you get the absolute path instead of the relative path. Fish does this.

FWIW I don't get it expanded to the full path on zsh, it's

./pants generate-lockfiles --resolve=mypy

Oh wait I remembered something bout this before https://pantsbuild.slack.com/archives/C046T6T9U/p1670317017087229?thread_ts=1670258242.955219&cid=C046T6T9U