-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
init-pants
action does not respect pants_bin_name
option
#9
Comments
Yep, looks like it uses Grepping pants_bin_name might be complicated? Config can come from a few different places (and anyway, you're not required to set that, it's just for help messages, you can still rename So I'd recommend adding an input to the job that sets the script name. We'd welcome a PR! |
Yeah, I think adding an input param to the action would be best here. Note that the action actually introspects the So, if you want to tackle this, please make sure to:
actions/init-pants/action.yaml Lines 41 to 46 in 615843b
|
Note: the |
I'm using the
pants_bin_name
option to point Pants to./pants-bin
. I've created my ownpants
script, which does two things:pants-bin
, passing in all arguments that were provided to thepants
script.This allows us to keep CodeArtifact authenticated and use Pants in the standard way.
Right now I don't think the
init-pants
GitHub Action respectspants_bin_name
option, and instead looks directly in./pants
, which prevents us from using the latest version of this GitHub Action. (I might be wrong here, I'm pretty new to Pants)Does it make sense to change the behaviour of this GitHub Action to check what
pants_bin_name
is (or perhaps the version of Pants), instead of having a look inside thepants
script itself? If there is a recommended approach, I'm quite happy to attempt this change myself!The text was updated successfully, but these errors were encountered: