npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests/ngit_init.rs, branch v2.0.1

test: refactor to use rstest more efficient test runs

2025-10-28T13:19:24+00:00

Identified high value areas to use rstest that would benefit most and refactored them

chore: bump nightly rustfmt

2025-07-16T09:59:20+00:00

to latest available and apply fmt fixes

fix(init): improve cli output

2025-05-23T11:43:30+00:00

for git push, a wait longer to allow ngit-relays to create repo

feat(init): overhaul & simplify with ngit-relays

2025-05-22T16:09:47+00:00

introduce ngit-relays as a way of setting git servers and relays at the same time using a standard for specific repo locations: https:////.git add simple and advanced modes. prompt less. eg always set remote origin to nostr url. automatically push main or master branch.

chore: bump rust-nostr v0.37 ~> v0.40

2025-04-01T13:35:50+00:00

and fix all of the breaking changes

chore: bump nix flake rust nightly `fmt` overlay

2024-12-16T09:46:30+00:00

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`

feat(init): set remote `origin`

2024-11-29T16:57:46+00:00

check whether remote `origin` is nostr url and if not attempt to set it.

test(init): fix cli white space issue

2024-11-29T10:21:24+00:00

otherwise the test never ends or fails

test(init): remove maintainers.yaml from tests

2024-11-29T10:05:19+00:00

as creation by default was removed in 9bee5f12efa5ed751468c68073c9122e12c22b5f

refactor: err msgs 'cannot' > 'failed to'

2024-11-26T12:26:47+00:00

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