if this is done in ngit the term is patch, I think, but in gitworkshop is just a proposal until merged, the term is also PR ( PP ) ( github is centralized, patch is PR, allready deployed )
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?
Discussion
No replies yet.