Global Feed Post Login
Replying to Avatar DanConwayDev

If any project maintainers comes across this warning when doing a `git fetch`. The easiest thing to do is to add a other commit and push it. It will update the nostr state and the git server. Another way is to add the git server as a remote and push directly to that.

If the warning is `n ahead` it means that someone has pushes commits to the git server and not to nostr. To prevent you inadvertently overiting those commits and lose them forever you can't push conflicting commits. You'll need to add the git server as a remote, pull the commits, which commit you want to be the head and for push to the git served remote and the nostr remote.

Avatar
Arjen 1y ago

That last point is I think what might have happened to me, I probably killed the process before a nostr commit happened and then made another commit. Interesting edge case...

Reply to this note

Please Login to reply.

Discussion

No replies yet.