publish doesn't work / pull-contributions loop?

[mechelon]

Description

Hey there,

I'm ready to publish a new version of my extension Can I PHP, but the publish command fails:

› npm run publish

> publish
> npx @raycast/api@latest publish

wait  - validate package.json file ..  /Users/dianascharf/Dev/side-projects/can-i-haz-php/package.json
ready  - validate package.json file
ready  - validate package-lock.json
ready  - validate other lock files
ready  - validate extension icons
ready  - validate extension metadata
ready  - run ESLint
ready  - run Prettier 3.2.5
ready  - getting fork
ready  - preparing clone
ready  - checking for new contributions
ready  - preparing extension
error  - pushing extension
failed running git Command failed: git push -u origin ext/can-i-php
error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date


error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date

I cannot really explain this error, however I tried to pull in contributions from the remote (even though there are none) by running npx @raycast/api@latest pull-contributions.

This gives the following output:

› npx @raycast/api@latest pull-contributions

ready  - getting fork
ready  - preparing clone
ready  - pulling new contributions
Some contributions conflict with your changes.

You can do two things:

- Decide not to merge but you won't be able to publish your changes. The only clean-ups you need are to run `git merge --abort`.

- Resolve the conflicts. Edit the files into shape and `git add` them. Use `git merge --continue` to seal the deal. You will be able to run `npm run publish` afterwards.

The conflict is the added top section of the previous changelog: e0b70a7
The problem is - I merge this conflicts, stage, commit and push all of them, which runs without error. However, publishing still fails, and when I run npx @raycast/api@latest pull-contributions again, I get the exact same output and merge conflicts again.

I tried to "re-fork" my extension from the Raycast action panel, but I get the following error:

Reason: An extension already exists with such name
Domain: commands
Time: 17:48:30.137

There's no extension/folder with that name in the directory I've chosen.

I could imagine that there's some kind of git mess but I cannot pinpoint the problems.

So, any ideas how to solve this?

Steps To Reproduce

No response

Current Behaviour

No response

Expected Behaviour

No response