This is basically pull request via nostr
thanks to nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 nostr:npub1x3azxuysp5vmfer4vgs4jn5tmfcx4ew8sh0qnev7gczljxsr7jwqa3g4el nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 and others who are accepting proposals for Amethyst, Damus, Gossip, Amber, Bostr and more via nostr
it would be great to see some contributors posting proposals for these projects
Discussion
Yes. I've been using the term 'proposal' as it can work like a PR or a patch/patchset depending on your preference. Perhaps it is too confusing?
It's confusing for newcomer. Thought that i was going to publish the entire git to nostr at first because it's "ngit" but turned out it's just for merge request.
Thanks for the feedback. Any ideas on how to make it less confusing?
You may rehandle or change `push` command name as something like `pr create`. It's really confusing for me as a starter.
Haha. I renamed it from `ngit pr create` to `ngit send` based on the conversations around nip34 as some people don't like PRs and i was worried it would be misrepresented as not nip34.
Clearly `ngit send` is not getting the message across.
