Haven’t looked into this just yet, but checking if...
# development
w
Haven’t looked into this just yet, but checking if anyone else has given any thought to this. Does the Pants GH action need to update any caches if moving to
scie-pants
? I’m assuming we don’t want to download the same pinterpreter if the
scie-pants
version hasn’t changed?
e
w
Whelp, that answers my question 🙂
I'm just thinking about the docs, where I think we recommend removing the
./pants
script
e
Yeah, I don't think a comprehensive think through was had when starting the acceleration campaign a few days ago. I'll need folks to step up and knock off issues. I had been plodding along and don't think others had paged in scope.
w
relatedly: this would go a long way toward making
scie-pants
easier to use in CI, since the curl-bash approach is more questionable there
e
The curl-bash we foisted upon ourselves though. My intention was get-pants.sh was checked into repos because we had not-Asher users say in slack they liked this feature for on-boarding. No curl, right there in the repo. The get-pants.sh name was used to convey you just need to run this once and to not start with p so pa<tab> did the right thing.
w
yea. i’d posit though that curl-bash might absolutely be the right thing for desktop usage, while being the wrong thing for CI usage.
e
But curl aside, I wrote that issue prior. I think integration was always needed regardless. After all
./pants
has been checked in forever.
w
yea