please provide feedback
this is an example ngit issue to demonstrate gitworkshop.dev.
please provide feedback with in reply to this issue or by creating a new issue.
please provide feedback
this is an example ngit issue to demonstrate gitworkshop.dev.
please provide feedback with in reply to this issue or by creating a new issue.
* `ngit clone` when?
* can i just do `ngit push -f` without making proposal and let it push the current commit to nostr relays instead
Re point 2: You can submit the latest commit as a proposal with `ngit send HEAD~1`. Is that what you mean or do you want to store the entire repo as nostr events and not use a git server?
I think it would make sense to show open only by default for 'ngit list'. So having an option to show all instead of an option to show only opened.
Yes. Maybe a tabbed view which starts on the 'Open' tab and other statuses could be selected via left and right arrow keys.
More simplistically, it could just show open proposals and accessing proposals with other statues could be achieved by providing its nevent in a command line parameter.
It would be nice to know how this project compares in functionality to https://radicle.xyz/
I did a comparison:
Very cool, thanks. I didnt realize that you wanted to reboot NIP-17, I've actually worked on it alot and it has evolved since then.
Thanks for the comparison.
This seems key: can be adopted alongside GitHub repositories
The radical token I think is something they might have given up on, and many are bitcoiners now, but i dont know the deets.
One thing radicle does is give a unique multi-hash for each repo. So I just shove them in an org called multi-hash (which I own on github too). It's a bit of a leaky abstraction tho.
Still learning more about ngit. Does each repo have its own unique identifier? I had played with nrepo for a while, but I'm moving in more direction.
Mixed thoughts on NIP-34, fiatjaf really stole my ideas without asking me. Nostr as we know it today would not exist if not for the git use case.
Unfortunatley I might be forced to compete with NIP-34 now, which is not what I wanted, but I hope we could find a way to cooperate.
Glad you're working on this, it seems great. My version will either be very popular, or not popular at all (1 user), so I think we dont step on each other's toes. Hopefully we can reuse stuff too!
Been diving into ngit a bit more. Pleasantly surprised so far! I will start using this.
This really is not bad. I think we can merge efforts.