npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests/push.rs, branch v1.2.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.2.02024-03-08T14:39:21+00:00feat(send): select commits from a list2024-03-08T14:39:21+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-08T14:37:56+00:00urn:sha1:6b3aecbcbde669859533716225e9c3bbfd2023b2
when since_or_range isn't specified
adds resilience as assuming master..HEAD can cause some issues
eg when master is not up-to-date with origin/master
test: ensure failed tests timeout2024-03-04T10:54:38+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-04T10:54:38+00:00urn:sha1:b02b4754c027bd751825c8e3b96766a5898187b1
resolve a long standing test issue where failures to output the correct
message in the cli would result in the test never ending
rather than failing
the many test cases updated in this change are to ensure
failures are caught rather than ignored
some of them are just refactored to remove calling an extra function,
which is no longer needed
note: this doesn't fix the intermittent issue, most commonly experienced
under the nix configuration, where tests that should pass
occationally never end preventing the rest of the suite from running
feat(send): add proposal revision cli msg2024-02-29T13:00:02+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-29T12:44:06+00:00urn:sha1:8de147768c2de3221d0a119278e76c013d20b0f1
before cover letter prompt
primarily this is to make it clearer that a proposal update
is being sent when using `ngit push --force` instead of
a new proposal
refactor: remove confusing options, improve help2024-02-23T10:11:56+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-23T08:30:15+00:00urn:sha1:b931b37e26486e4e6d15f302e87141dcf2f596ba
from_branch and to_branch have been replaced
by specifying revision ranges
feat(push): add `--force` to issue revision2024-02-23T08:15:24+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-23T08:15:24+00:00urn:sha1:84d8f03cf2471d3530f4657055f272474880b6b5
wrapping `send --in-reply-to` unless branch up-to-date
refactor: tweak error wording2024-02-20T12:17:25+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-20T12:17:25+00:00urn:sha1:570ad62875c191c6bb7809e936a64938eb0fb310
remove the word nostr for consistency and as its a bit confusing
refactor: rename PR to proposal2024-02-16T22:31:29+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-16T22:31:29+00:00urn:sha1:701668b02d999af42f51d8bd25fffb2a8692c3c8
PR is a problematic term when it ambiguous whether the
set of patches are PR-like or email-patch like.
fix: improve 'searching for profile updates' msg2024-02-15T10:21:09+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-15T10:21:09+00:00urn:sha1:fc63ee3466ed5088cedb278d2b56a989668f273c
it wasn't clear why no results were coming back from relays
or why it is needs (added reference to relay updates)
feat: send to default relays, blast repo event2024-02-14T13:47:11+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-14T13:47:11+00:00urn:sha1:a1d67c50c8ebc5395b069e30b60d66e0c7de5a5a
improve the distribution of events by sending to default relays
in addition to user and repo relays. for better discoverability of
repo events, this is also blasted.
a temporary fix to blast everything was removed.
the less reliable purplepages.es relay is moved to
more_fallback_relays that currently isn't used
feat!: move `prs create`>`send`, `prs list`>`list`2024-02-14T08:47:27+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-14T08:41:02+00:00urn:sha1:c0847f928c32adb0b4dfc3b73ee77fa3cdb5ec21
remove unnecessary hierachy of `prs` which is also a troublesome term
replace the concept of `create` which aligns more to the PR github model
to `send` which aligns more with the git patch model