Replying to Avatar DanConwayDev

I pushed the repo state event (kind 30618) to the relay at http://localhost:8484.

when add the git server as a remote and try and push the main (only) branch at the commit in the state event I get the error:

```

git push song

XML error: syntax error

error: no DAV locking support on http://localhost:8484/

fatal: git-http-push failed

error: failed to push some refs to 'http://localhost:8484'

```

song on the cli reports:

```

when i add the git server as a remote i get the error:

7:01PM INF request method=GET url=/info/refs?service=git-receive-pack

7:01PM INF request method=GET url=/HEAD

7:01PM INF request method=PROPFIND url=/

7:01PM WRN failed to load repo error="failed to get commit at 'HEAD': failed to get head: reference not found" repo=ca118aa

```

when I visit the http://localhost:8484 in a browser song cli reports:

```

7:02PM INF request method=GET url=/

7:02PM WRN failed to load repo error="failed to get commit at 'HEAD': failed to get head: reference not found" repo=ca118aa

7:02PM WRN failed to load repo error="failed to get commit at 'HEAD': failed to get head: reference not found" repo=gitworkshop

7:02PM WRN failed to load repo error="failed to get commit at 'HEAD': failed to get head: reference not found" repo=ngit

7:01PM WRN failed to load repo error="failed to get commit at 'HEAD': failed to get head: reference not found" repo=ngit

```

None of this makes any sense to me. If you are doing a normal git push it should work because that's the only thing I tried.

Reply to this note

Please Login to reply.

Discussion

seeing these comments in my non git client is interesting...

Interesting good or interesting bad? Most of these conversations will *probably* move to nip22 soon.

Kind 1111, for the win.

Only if users get notification in their daily driver clients. Otherwise the conversations die and move to a channel where participants do get notifications.

For me it makes sense for clients that aim to be the daily driver to have notification systems that show 'other stuff' related notification somehow group together and give the user choice about how they see them. For example, maybe the dont want to see git related conversations outside of work hours.

This is what DVMs are for

What role to you think DVMs should play in notifications?

When I say DVM I often actually mean bot. It could just be a bot. Launch it yourself, or pay a DVM to notify you. Idk. There are lots of options.

This feels inelegant to me. Would they DM me? I'd like more control and from my daily driver app than a bot could provide.

Notifications are just your client fetching stuff from a server, so there is no point in having a bot or a DM or anything like that except as a workaround.

that would make sense

it would be really annoying if your github issue went viral on social media lol

Nothing like an incentive to get the issue resolved

Sounds like a foss win if its a public repo

You didn't have to do anything to provision the repository first?