You may rehandle or change `push` command name as something like `pr create`. It's really confusing for me as a starter.

Reply to this note

Please Login to reply.

Discussion

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.

Maybe `ngit send` should be `ngit pr create` and `ngit push` should be `ngit pr update`?

Creating a new lexicon (proposal) for well established developer workflows was probably a bad idea as it was always going to cause confusion.

I think I prefer this