extensions: can't publish using the `npx ray publish` tool

Alright, I’ll make the error messages more explicit and close this issue as the OP was fixed a while ago

Sparse-checkout isn’t particularly new and it is indeed what ray publish uses under the hood

I was more thinking about reading the local git config when you run ray publish to use the same in the fork

it will only download the current extension folder without any git history,

That’s the point yes. The goal is to abstract the flow away from this repo.

I don’t want to commit using the global git config

How do you usually commit if not using the global git config?

I noticed that in the package.json file, the order of the json of the downloaded version is different from the origin main branch.

Yeah that’s a bug that will be fixed in the next release

right so for some reason git remote get-url origin doesn’t fail on your computer when we run it in the ray CLI, even tho it fails when you run it in your terminal 🤔

I’ll have a look. In the meantime, you could push your repo to github repository so that there is a remote…