npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/bin/ngit/sub_commands/init.rs, branch v2.2.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.2.02026-02-20T21:21:52+00:00use trusted maintainer's grasp servers as fallback for co-maintainers2026-02-20T21:21:52+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T21:14:45+00:00urn:sha1:b10340cb00a00da07d0ae735796d83801454779e
when a co-maintainer has no grasp servers of their own, fall back to
the trusted maintainer's grasp servers rather than jumping straight to
system defaults. if the trusted maintainer only uses a single grasp
server, the first system default is appended for redundancy. system
defaults are only used when neither the user nor the trusted maintainer
has any grasp servers configured.
update relay prompt to reflect grasp servers are sufficient2026-02-20T21:21:50+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T20:31:33+00:00urn:sha1:4295e4a3aaca29fda73a955186d30641815d4efa
Public relays are no longer recommended; grasp servers cover relay
needs. The interactive prompt now reflects this.
drop default relays from announcement events2026-02-20T21:21:49+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T20:26:31+00:00urn:sha1:724e02ac8c538e9dfe4faa072082fad301e49b10
ngit init and accept_maintainership_with_defaults no longer seed relay
lists from the client default set. The relay list in a Kind:30617
announcement now contains only grasp-server-derived relay URLs; no
additional public relays are suggested or added automatically.
extract grasp/maintainership helpers to lib and auto-accept on push2026-02-20T21:21:48+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T20:09:09+00:00urn:sha1:64747526c9f6ab43f9dac461d056bb42992573b4
move apply_grasp_infrastructure, latest_event_repo_ref to lib/repo_ref.rs
and wait_for_grasp_servers + grasp_servers_from_user_or_fallback to a
new lib/accept_maintainership.rs so both binaries can share them.
add accept_maintainership_with_defaults which publishes the co-maintainer's
own Kind:30617 announcement with defaults (user grasp servers, shared
metadata from existing events) then waits for grasp server provisioning
and updates nostr.repo config and origin remote.
replace the push error block with a call to accept_maintainership_with_defaults
so pushing now silently accepts co-maintainership instead of failing.
improve ngit init messaging for co-maintainership acceptance2026-02-20T20:43:47+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T12:08:37+00:00urn:sha1:1583a5f5b137ec408d9358c12f6716f7033a2c69
when a co-maintainer runs ngit init, it now clearly states upfront
that they are accepting a co-maintainership offer (not creating a
new repo), shows who offered it, and on completion confirms the
acceptance and explains they can now push. updating an existing
co-maintainer announcement also gets its own clear message.
fix: remove outdated patch_supports gate and fix fetch parent fallback2026-02-18T22:00:35+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T22:00:35+00:00urn:sha1:56b3c149df70af5d441e8527ec1225e5038bde8e
Remove the patch_supports_commit_ids gates in checkout.rs and list.rs
that pre-dated the mbox fallback logic. apply_patch_chain already
handles all fallback cases. Also replace the main-branch TODO fallback
in make_commits_for_proposal with get_parent_commit_from_patch, which
uses timestamp-based best-guess when the parent-commit tag is absent.
feat: support PR-format proposals in ngit apply2026-02-18T13:10:24+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T12:38:37+00:00urn:sha1:e6bb9effa194fe63b5e969c090dbe6e93f13d312
Instead of erroring when a proposal uses PR format (kind 1618/1619),
ngit apply now fetches the tip commit from git servers, determines the
base commit via the merge-base tag or by walking ahead of main, generates
patch text for each commit using git2, and applies via git am.
Also fixes a bug where clone-tag server hints were silently skipped in
the fetch fallback, and refactors the git-am invocation into a shared
helper to avoid duplication between the patch and PR code paths.
fix: preserve grasp server order in relay hint for nostr url2026-02-18T13:01:01+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T10:12:45+00:00urn:sha1:eb3860359cfc2f2bab95a546bd6003091584b918
apply_grasp_infrastructure was inserting each grasp relay at index 0,
causing later servers to displace earlier ones. the last server in the
list ended up as relays[0] and thus the url relay hint, reversing the
intended priority order.
report event kinds in publish progress messages2026-02-18T13:01:01+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T09:50:57+00:00urn:sha1:ef53dce22cb363d9b373cae033f4be91f6cfb194
instead of generic 'Publishing to nostr relays...' messages, describe
what is being published e.g. 'Publishing 3 patches to nostr relays...'
or 'Publishing 1 announcement and 1 state event to nostr relays...'
poll grasp servers for readiness instead of fixed 5s wait2026-02-18T13:01:00+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T08:00:18+00:00urn:sha1:10f5dd5f48659d6e99abc762d46be397d24b48d9
Replace arbitrary 5-second countdown with active polling of grasp
servers during ngit init. Servers are checked every 1s with a 7s
timeout (2s in tests). Shows progress like '1/2 grasp servers ready'.
Grasp servers return 404 until the repo is provisioned, so we poll
until they accept git connections. Proceeds anyway on timeout rather
than failing, since some servers may still be initializing.