Replying to Avatar DanConwayDev

as users who have used ngit to create proposals / repo events and interact with them on gitworkshop.dev, what level of information would have helped you grok what you need to grok?

nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg nostr:npub1896p07z8xngpct5ma00mdrad4gqfnwfwdqcl706wrm25ajynahhs27x5ge

Would calling proposals PRs help? How can we communicate the enduring need for a source git repo but not forks?

39
purple.co 1y ago

PPs , Patch Proposals. easy to type .

Reply to this note

Please Login to reply.

Discussion

39
purple.co 1y ago

PRs make sense for github as a centralize model (top-down) with git hub as single reference ( relative to central ), ngit is like git ( bottom - up ) and have local repository as reference, but is expose as patch ( relative to local ).