npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests/git_remote_nostr, branch v2.4.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.4.02026-02-26T16:35:59+00:00fix: correct merge-base in PR events from git push of pr/ branch2026-02-26T16:35:59+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-26T16:35:59+00:00urn:sha1:01aeb2a3265bcafa162987c85dd281981770bba7
When pushing a pr/ branch, the ahead slice is reversed by callers before
being passed to generate_patches_or_pr_event_or_pr_updates, making it
oldest-first. The tip/first_commit assignments were backwards (using
first()/last() as if the slice were youngest-first), so the merge-base
was computed as the parent of the PR tip rather than the parent of the
oldest commit. Multi-commit PRs therefore showed only 1 commit when
applied via ngit apply.
Adds an integration test that pushes a two-commit large-file PR branch
and asserts the merge-base tag equals the main branch tip.
fix: advertise only state events with resolvable git objects2026-02-26T15:26:20+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-26T14:00:12+00:00urn:sha1:d8b85cbce5cba9bfb8b15a8bd5c1b7200ff3e488
git-remote-nostr now walks the per-relay state events captured in
FetchReport::state_per_relay (newest first) and advertises the first
one whose every OID is either present on at least one git server
(confirmed via list_refs) or already available locally. If no such
state event exists it falls back to the raw git server state.
Previously the latest nostr state event was always used regardless of
whether its OIDs had been pushed to any server, causing catastrophic
missing-object errors during clone or fetch when a state event was
published ahead of the corresponding git push.
fix: apply push-options to patch series generation2026-02-17T15:09:03+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-17T12:44:13+00:00urn:sha1:4cbba068d1ddbd14ba41d75def3ae266989aced8
The title and description push-options were previously only applied to PR
creation but not to patch series generation. When force-pushing to update
an existing patch series, the custom title and description were ignored.
This change passes the title_description parameter to the patch generation
function, allowing users to customize patch series cover letters via:
git push --force --push-option=title="Title" \
--push-option=description="Description" origin branch
Includes integration test for force-pushing patches with custom cover letter.
feat: support multiline descriptions in push-options via \n escape2026-02-17T14:04:32+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-17T12:11:33+00:00urn:sha1:5cc8ae28cb462d2cb0b7f74dfa5238e62d17eb70
Git push-options are line-based so literal newlines cannot be sent.
Users can now write the two-character sequence \n which is decoded
into real newlines before publishing. Use \\n for a literal backslash-n.
Includes unit tests, integration test, help text, and changelog entry.
feat: add push-options for title and description to git-remote-nostr2026-02-17T11:38:26+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-17T10:42:33+00:00urn:sha1:fe5addc2a61022824e83c3523a83fce7690ca8e8
Allows setting PR title and description via git push options:
git push --push-option=title="My PR" \
--push-option=description="Details" origin pr/branch
feat(list): make list async and include sync report inline2025-11-13T22:08:56+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-13T17:18:35+00:00urn:sha1:82c7a95f6e9aa266d2f0d2035a0ce4f1715b62ad
copy relay fetching approach to async and reporting
fix: out of sync grasp server cli output2025-11-13T14:49:00+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-11T08:31:46+00:00urn:sha1:65f3bd360c065aca493eddf7eb5d3d8191a84b56
so it shows a summary rather than a lot of lines of issues
fix: cli output line deletion during fetch2025-11-13T14:40:09+00:00DanConwayDevDanConwayDev@protonmail.com2025-11-11T07:21:08+00:00urn:sha1:52370f542dad87ab029a5d701cc46658d5aef91b
also reduce the clutter in the cli output for grasp servers.
test: refactor to use rstest more efficient test runs2025-10-28T13:19:24+00:00DanConwayDevDanConwayDev@protonmail.com2025-10-28T13:19:24+00:00urn:sha1:a287f53132c91eaa3ba8d5e9c2bec80587316aad
Identified high value areas to use rstest that would benefit most and
refactored them
fix(remote): `refs/pr-by-id/*` ~> `refs/pr/*/head`2025-09-03T15:57:14+00:00DanConwayDevDanConwayDev@protonmail.com2025-09-03T15:57:14+00:00urn:sha1:4bd46c3cf7bacb062d45d3c99d3edfadc95cb139
to align more closely with githubs `refs/pull/*/head`
we can pretend that pr means both Patch Request and Pull Request