npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/test_utils/src/git.rs, branch v2.4.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.4.12026-03-30T16:29:23+00:00feat: git worktree support2026-03-30T16:29:23+00:00m0werm0wer@sgn.space2026-03-29T14:45:52+00:00urn:sha1:820fd706a24be7a58554a27e411e120cfa28d9a6
Git worktrees don't have a .git directory with a parent, so we need to
look for the git dir via git2's Repository::discover() and then look for
the cache database there. This allows the client to work correctly when
run from a worktree, and also allows the cache database to be shared
between the main repo and its worktrees (since they share the same git
dir and thus the same cache path).
feat: update ngit init for non-interactive mode2026-02-10T13:03:37+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-10T12:52:19+00:00urn:sha1:09bb21462ac5571cace5a7e71103156772a499fe
Complete rewrite of ngit init to support non-interactive mode by default.
Key changes:
- Implement hybrid validation (validate all args upfront, fail fast)
- Add --grasp-servers flag for specifying git servers
- Prefer --name over --identifier for better UX
- Add comprehensive validation with helpful error messages
- Support both clone and init-from-existing-repo workflows
- Add --force flag to bypass safety checks
- Update tests for new non-interactive behavior
- Add test utilities for non-interactive testing
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 rust-nostr v0.37 ~> v0.402025-04-01T13:35:50+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-01T13:31:34+00:00urn:sha1:948fe972eb2bddf187b79f2673a091b6331cfd90
and fix all of the breaking changes
chore: bump rust-nosrt v0.37.02024-11-27T17:08:25+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T17:08:25+00:00urn:sha1:83448a99aaf18c7a045a081c5de0c22bc4a83de1
use RelayUrl in repo_ref which I had resisted as it mutates relay
urls when printed to append a slash
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
chore: bump rust-nostr to patch near v0.36.02024-10-28T15:41:14+00:00DanConwayDevDanConwayDev@protonmail.com2024-10-28T15:41:14+00:00urn:sha1:ae87aedae9696f4c855ac3dc47e61faec9d07c15
bump all rust-nostr packages
refactoring code based on breaking changes
upgrading to patched version to address signer issue:
nostr:nevent1qvzqqqqqqypzq6xcz9jerqgqkldy8lpg7lglcyj4g3nwzy2cs6u70wejdaj7csnjqy88wumn8ghj7mn0wvhxcmmv9uqzpsw5ph8le2n2kh6uchftawt74hddazk9tp7wjmz967y2l0uva5rc7hsstq
chore: bump rust-nostr v0.352024-09-25T13:37:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-25T13:37:17+00:00urn:sha1:d6faad17e814d252a72e3aca39a4b3898382bab9
bump all rust-nostr packages
feat(remote): `push` force push proposal2024-08-08T16:36:44+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-08T16:34:40+00:00urn:sha1:9971f23a184d57600ea9b1962910d32bf6aec185
will issue a proposal revision
test(remote): `push` to existing proposal2024-08-08T14:01:32+00:00DanConwayDevDanConwayDev@protonmail.com2024-08-08T13:58:29+00:00urn:sha1:b53251925e8cf0393377633ec1012f0613e7c42b
push 2 commits to an existing proposal
there are a lot of asserts in here but if they were split out into
their own tests the suite would take much longer to run as we are
waiting a few seconds in the test to ensure the
timestamps are different