npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/bin/ngit/sub_commands/send.rs, branch v2.2.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.2.12026-02-10T13:03:39+00:00feat: update ngit send for non-interactive mode2026-02-10T13:03:39+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-10T12:52:26+00:00urn:sha1:3383477386916e82a19fa1e9c4d95b232ba0a40e
Rewrite ngit send to support non-interactive mode:
- Add validation for required arguments (title/description)
- Add --force flag to bypass commit suitability checks
- Add --no-cover-letter flag to skip cover letter
- Improve error messages for missing required fields
- Update title/description/cover-letter logic for non-interactive mode
- Add comprehensive tests for non-interactive behavior
feat(send): add `merge-base` tag to PR (Update)2025-10-17T09:20:43+00:00DanConwayDevDanConwayDev@protonmail.com2025-10-17T08:30:35+00:00urn:sha1:2bf98e91e5b5a7d1b18557e65711b5ef3d1a54a3
following its inclusion in the NIP-34 spec
feat(send): add `force-pr` or `force-patch` flags2025-10-10T16:25:49+00:00DanConwayDevDanConwayDev@protonmail.com2025-10-10T16:25:49+00:00urn:sha1:0e8fcc743b343c620a6723f5ad517ab98f140401
so users can choose when there commits are too big or small instead
of relying on the 60kb rule
feat(remote): use push PR non-interactive fallback2025-09-04T11:09:06+00:00DanConwayDevDanConwayDev@protonmail.com2025-09-04T11:09:06+00:00urn:sha1:8527646022abdb290222a45314d090eef0871cae
move the PR push code in 'ngit send' into lib.
reuse the non-interactive fallbacks in git-remote-nostr
fix(send): PR cli output2025-08-07T16:40:34+00:00DanConwayDevDanConwayDev@protonmail.com2025-08-07T12:02:08+00:00urn:sha1:896267959bc9e436d7c5d2ee0ff8c8c088fc7274
to keep the user informed of whats happening / happend
refactor: rename fn `is_grasp_server_in_list`2025-08-07T16:25:54+00:00DanConwayDevDanConwayDev@protonmail.com2025-08-07T07:41:39+00:00urn:sha1:afaa472196059bbfbd41a39b23d8ffb4c28d0805
to make it's purpose clearer
fix(send): print event description before publish2025-08-07T16:25:52+00:00DanConwayDevDanConwayDev@protonmail.com2025-08-06T15:25:42+00:00urn:sha1:28d0ab562d3e0f62a56821cd503ed9d9d5e4610f
so its clear from the TUI what has just been sent
feat(send): PR fallback to user / custom grasp2025-08-07T16:25:50+00:00DanConwayDevDanConwayDev@protonmail.com2025-08-06T11:52:59+00:00urn:sha1:a9b2ebf8216be34950e54dd9a446dbdc0c9c744a
if use is maintainer, push PR to all repo git servers.
if user has a fork, push to all git servers it lists, and repo
grasp servers.
if user hasn't got a fork but has a user grasp list and pushing
push to repo grasp servers fails, create a personal-fork
automatically at each user grasp server and push there.
fallback to prompting user for either grasp servers or git server
with write permission.
if user provides grasp servers, suggesting adding to user preference
list.
feat(send): custom ref for PR clone url2025-08-06T15:00:58+00:00DanConwayDevDanConwayDev@protonmail.com2025-08-05T10:38:09+00:00urn:sha1:29f61ffdf155ea88b8d9aec23d28cf70baba577e
allow specifying ref for pushing PR to custom clone url
feat(send): push PR to custom clone url2025-08-05T10:08:26+00:00DanConwayDevDanConwayDev@protonmail.com2025-08-05T10:08:26+00:00urn:sha1:dee39c39116773fde22c4fe30a87d54d1d3658e2
if the repo doesnt list any grasp servers, or pushing to them fails