Strange failures, not sure how to recover about action

[Andarist]

Omg, I was somehow sure this thread was in the main Changeset repo. My bad 😅

[Andarist]

Im afraid that it doesnt give us a lot of info to work with. It would be great if u could try to debug on which command it fails - maybe that would shed a little bit more light on your case as your setup doesnt look anything different from the standard setup that a lot of other projects use without much of a problem 🤔

[pngwn]

Yeah, I sadly wasn't getting a great deal of info but I think I have figured it out.

I had commit: true in my config file which actually explains why the working tree was clean when commiting after running the version script. I'm not sure if this is a required setting when using the action but it seems to have solved my problem here. If it is required it may be worth documenting (which I'm happy to do if you point me), but it could be some funkiness around my setup also, I am using pnpm which complicates things a touch.

[Andarist]

I have actually forked your repo in the meantime and tried to play with it a little bit but didn't have any noteworthy results 😅 It's great that you have figured this out! I would have not guessed that git returns 1 when trying to commit on the clean working tree - the message itself doesn't sound like an error or anything. I've somewhat confirmed that this was probably the culprit by trying to execute:

require('@actions/exec').exec("git", ["commit" ,"-m", "test"])

which results in the very same error you have encountered.

I believe this is an oversight on our part - this should be handled more gracefully. Could you report this to https://github.com/changesets/action ?

[pngwn]

Sure thing. Thanks for looking into this!

[pngwn]

Hold on, isn't that where I am now?