Hi all, I'm trying to update our GHA script to use scie-pants. With

pantsbuild/actions/init-pants@v4-scie-pants

, when running

pants tailor --check ::

I'm seeing this cryptic message:

Would create BUILD:
  - Add shell_sources target root

To fix `tailor` failures, run `pants tailor`.
Error: Process completed with exit code 1.

I don't have anything named

root

in my repo. Also, when running tailor command locally, it succeeds. Is this something GHA creates? Any workaround on this issue?

The only difference between

scie-pants

(

pants

) and

./pants

is that scie-pants will search up from the CWD it is invoked in for

pants.toml

whereas

./pants

is naturally rooted in the root of your repo side-by-side with

pants.toml

. Is CWD what you think it is in CI? Is it the repo root?

yeah I do have

pants.toml

in the root dir of the repo, and I used to run

./pants

instead of

pants

and it worked fine, so I'm not really sure what's changed

Was the gha yaml diff just the action update and exactly only

s|./pants|pants|

?

yes. that and the change to

pantsbuild/actions/init-pants@v4-scie-pants

from

...@v2

Ok, yeah - makes no sense.

maybe the action is leaving the

get-pants.sh

script lying around?

That wouldn't matter. Its generally encouraged / fine to check that script in.

I see that the python example repo isn't doing tailor in its GHA, might be something we want to check there as well? sorry I saw that it does do that.

it matters if it’s not checked in (and therefore has no target in the root

BUILD.pants

)

Ah, yes. That's a difference from the local repo. Gotcha.

yeah this step needs to

rm

the script after running it: https://github.com/pantsbuild/actions/blob/v4-scie-pants/init-pants/action.yaml#L65-L76

That's fine in a whac-a-mole way but is generally a disaster. If all GHA actions are checked out as subdirs to the cloned repo root, this will be an ever-present and growing problem. Pants gains 1st class js support and now starts seeing js actions files, etc.

the latter

Ah, there should be no rm then - it just shouldn't materialize files there at all ever.

@boundless-zebra-79556 I think you can unblock yourself for now by throwing an

rm get-pants.sh

into your CI job before you run

pants tailor --check

, if you’re under pressure

Or even a .gitignore entry.

Yeah .gitignore makes the most sense! Will do, thanks!