Replying to Avatar fiatjaf

You mean a state event should exist on the server? Or the code should be available on the server? Does git-remote-nostr try to fetch the remote refs before pushing?

Let's suppose a remote state exists on the server, it says the branch "master" points to commit "01010202". Why is that useful if I just want to say "master" now points to "11112222"? Won't it be replaced?
Avatar
DanConwayDev 1y ago

the server should respond to a 'list' request with return the refs.

the remote helper tries to get the refs on the remote server so it can check if there is a conflict.

in git push should only work if its a fast-forward commit unless the `--force` flag is used.

Reply to this note

Please Login to reply.

Discussion

Avatar
DanConwayDev 1y ago

if a state event has been issued (so state is being managed on nostr) the remote helper still checks the refs on the git server(s) to add protections to reduce the likelihood that another maintainer pushes a conflicting change at about the same time which gets overwritten.

Also covering the scenario where there owner or another maintainer starts pushing directly to the git server (by passing the state on nostr). in this case the latest conflicting changes on the git server shouldn't be automatically overwritten without the owner being warned about it.