npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/git/mod.rs, branch v1.6.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.6.12024-12-16T09:46:30+00:00chore: 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`
fix: defend against empty`tags`2024-12-12T11:32:48+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-12T11:31:51+00:00urn:sha1:6f45aa9937602f3d03cd83cfb5fb3c541fac4adf
prevent a panic when tags are of an unexpect length
feat(init): set remote `origin`2024-11-29T16:57:46+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-29T16:09:38+00:00urn:sha1:8c763d0483309c85a32a7f4a20ba0279083ee40f
check whether remote `origin` is nostr url and if not attempt
to set it.
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
feat(login): overhaul login experience2024-11-21T16:53:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-21T16:53:17+00:00urn:sha1:f79014235e85554e3661b3f2a02b8fa88bc192ff
* simplify login menu, making it more accessable to newcomers and
easier to select remote signer options
* enable `ngit login` to work from anywhere (not just a git repo)
* assume fresh login details saved to global git config but fallback
to local repository
* maintain local repository login via `ngit login --local`
* maintain login via CLI arguments eg `ngit send --nsec nsec123`
* nudge users to remember nsec when pasting in ncryptsec for a
better UX, whilst maintaining the option to be prompted for
password everytime
* create placeholder menu items for help menu and create account
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
fix(login): locally when globally logged in2024-09-24T18:48:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-24T18:38:00+00:00urn:sha1:635b5b119e7719a66d064853c3cb4c03872abfa9
as it would fail to save to local git config
fix(remote): add resilience to `prs`2024-09-23T12:36:53+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-23T09:46:26+00:00urn:sha1:2cdbb8c7ac6c98af6e36c4458c08bef2299794e1
make poorly formatted patches fail silently. we stop trusting that the
`commit` tag in the latest patch can be produced by apply the patches.
to achieve this we must recreate the commit during the list command,
which require fetching the parent oids.
support patches without optional `commit` and `parent-commit` tags.
test: fix gitlib2 version in sample2024-09-18T12:10:37+00:00DanConwayDevDanConwayDev@protonmail.com2024-09-18T12:10:37+00:00urn:sha1:e863ee5e2172cd7d2cd7a903d138bd839de4972d
so they match v1.8.2 used in updated git2