npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/bin/git_remote_nostr/push.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-05-31T18:50:06+00:00feat(push): prevent push if no ann event2025-05-31T18:50:06+00:00DanConwayDevDanConwayDev@protonmail.com2025-05-31T14:34:21+00:00urn:sha1:5f45edbebe310decb06f955d95665a6ad387c6cb
To ensure additional maintainers publish an annoucement event,
require it for them to push
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(send): add description to event signing process2025-04-03T16:13:50+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-03T16:13:50+00:00urn:sha1:29688c2cfe32a27dd9faabd66691f6db1cd4818a
resolving
nostr:note1qu8le4a8qz9hhxy6q85txejcq0kln0r3s9vdtwrhtqwvauc6nxuqn3fj0z
so it doesnt appear frozen when there are lots of events being signed
by a remote signer
fix: allow soft push if not behind server2025-04-01T13:45:36+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-01T13:45:36+00:00urn:sha1:34d12345e8993e8df367d68a09fd041296c22559
when nostr and the gitserver are out of sync an error was thrown when
the git server was behind during soft push. It should only throw
the error if its ahead of the tip to be pushed.
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
fix(push): find existing proposal2024-12-20T10:17:28+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-20T10:01:03+00:00urn:sha1:4bab25d575fa82785a424038e517b09e9485bad3
improve reliability of getting current logged in user to assess if
they have submitted a proposal with the same name / branch name
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