npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests/ngit_login.rs, branch v2.4.2Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.4.22026-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
chore: nix flake update2025-10-17T16:18:47+00:00DanConwayDevDanConwayDev@protonmail.com2025-10-17T14:22:05+00:00urn:sha1:4a9dcc66ac7be69031a19f6ece0be4642e1f3057
update nix dependancies including hardcoded nightly.rustfmt
applied autofixes
chore: bump nightly rustfmt2025-07-16T09:59:20+00:00DanConwayDevDanConwayDev@protonmail.com2025-07-16T09:59:20+00:00urn:sha1:ac53bca7e315848864ff9e51703720b5b466bc42
to latest available and apply fmt fixes
chore: nix flake update2025-07-16T09:39:35+00:00DanConwayDevDanConwayDev@protonmail.com2025-07-16T09:10:41+00:00urn:sha1:092b9606ff2b721d858a5c7b2b27a2f9942b4bc4
required running:
`cargo fix --allow-dirty --allow-staged`
`cargo clippy --fix --allow-dirty -- -D warnings`
to fix problems
and then manually fixing some too
chore: bump nix flake rust nightly `fmt` overlay2024-12-16T09:46:30+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-16T09:00:46+00:00urn:sha1:4ee83e2fe5335a8afd78439c35f029c4a472e797
update the rust nightly `fmt` overlay which needs to be pinned
to a specific version (this case by date)
update formatting in main files via `cargo fmt`
test(login): fix `login` nested under `account`2024-11-27T14:51:24+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T14:51:24+00:00urn:sha1:469787a93c6732706e040d82bb28d869afc49f20
this was missed during a find and replace
feat(account): move login/out cmds to account2024-11-27T09:44:24+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T09:42:37+00:00urn:sha1:cb92d2ac8a7e014eac28ddf9ad1e6500b840739f
move login, logout export-keys commands to sub commands under account
test(login): update `ngit login` test2024-11-26T16:28:09+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-26T16:28:09+00:00urn:sha1:bdf71cb3d5a5ff8399c10c8d2492d3dd01c5fa33
to reflect the new interface and testing only nsec login
refactor: err msgs 'cannot' > 'failed to'2024-11-26T12:26:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-26T07:48:30+00:00urn:sha1:a0593e3aa9b19b9ca3c3881cbe0d9d207fe46d2c
in nearly all cases 'cannot' was used when an action was tried and
failed. 'failed to' is strictly better because:
* just because the action didn't work that time doesnt mean it
cannot work
* it is better at drawing the users attention to a problem
test: fix login copy2024-11-25T12:59:43+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-25T12:59:43+00:00urn:sha1:1fe1b917b71f6897deaf89f5ee725614cba9b693
appended 'via cli arguments' to 'logged in as fred' during login step