npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/bin/git_remote_nostr/list.rs, branch v1.7.2Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.7.22025-06-02T12:26:16+00:00fix: ignore dereferenced tags in state2025-06-02T12:26:16+00:00DanConwayDevDanConwayDev@protonmail.com2025-06-02T12:26:16+00:00urn:sha1:e45b6284c54ed0e4ff7a9428c92087aa3f8e3cfc
as they are just noise
feat(push): avoid out of sync issues for ngit relay2025-05-23T20:53:35+00:00DanConwayDevDanConwayDev@protonmail.com2025-05-23T20:53:35+00:00urn:sha1:a75a1441b7c1cec93ebc0cb796c21360abbc5573
we need to be careful with git servers with their own permissions so
a ngit user doesn't inadvertantly push changes on top of a another
user who pushed directly to the git server without using the
force flag.
We dont have this problem with ngit-relay so we can always force
push, even if the user didnt as nostr is the authority of state.
feat: only try http(s) for ngit-relays2025-05-23T09:01:29+00:00DanConwayDevDanConwayDev@protonmail.com2025-05-23T09:01:29+00:00urn:sha1:686604665395385600ef8f1b5238a775249552a1
otherwise it tries all the protocols and reprots on each
fix: always try git servers over other protocols2025-05-09T19:00:24+00:00DanConwayDevDanConwayDev@protonmail.com2025-05-09T19:00:24+00:00urn:sha1:38969bbfadf2854f6acb1e515f8f388a01a018c2
remove the code that guessed whether it was an authentication failure
and gave up is it wasn't. this prevents it from trying http for push
when ssh is not supported eg. ngit-relay
chore: nix flake update2025-05-05T20:30:59+00:00DanConwayDevDanConwayDev@protonmail.com2025-05-02T13:37:14+00:00urn:sha1:a744f4aae9ffee9dd246090bef486b09433778d0
update nix dependancies to latest version using default update options
run `cargo clippy --fix` and `cargo fmt` to fix new clippy errors
feat(remote): include draft PRs2024-12-20T10:25:22+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-20T10:25:22+00:00urn:sha1:97de61aef110414bad8a1a3f8506e9c1efb37402
show draft as well as open PRs as remote branches
refactor: branch_name handling2024-12-20T10:17:27+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-20T09:59:14+00:00urn:sha1:316f858f223162408cfd52183ef7645828c2f480
improve clarity by renaming variables and methods
defend against `branch-name` tag with an unsafe name
refactor: use nostr url from repo_ref2024-12-20T08:07:22+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-20T08:07:22+00:00urn:sha1:8cc4a21061433c9a29e36c4f33e4d84bea1defee
simplify to allow the removal of warning:
`#[allow(clippy::too_many_arguments)]`
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`
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