npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests/send.rs, branch v1.1.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.1.12024-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): fix grammar in cli output2024-03-01T14:49:48+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-01T14:49:48+00:00urn:sha1:8519dc4a10d47747e6df3f47e25c36bf16befe00
refer to a single patch as patch rather than patches
feat(send): when on main default to sending 1 patch2024-03-01T14:49:13+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-01T14:49:13+00:00urn:sha1:445eea13d987b345535fd4fa56486ff334bbd351
based on feedback from santos:
nostr:31c085a584cbd30f71a44a70eaf828c2c8c5f6e3efb7942547edb37cf4a632cf
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
fix: branch-name specified as main or master2024-02-28T16:38:39+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-28T16:38:39+00:00urn:sha1:d4ef8cad0b95baa67e0f2803a7ec8601754a82a7
branch-name should be ommitted or ignored if
patches created on main or master
instead it should be infered based on commit msg
fix(push): remove force push bug2024-02-23T12:25:11+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-23T12:25:11+00:00urn:sha1:a9e4c6772a378fd28edbca9b9267d2e7d08bee2c
introduced in b931b37e26486e4e6d15f302e87141dcf2f596ba
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(send): in-reply-to arg for revised proposal2024-02-21T15:01:11+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-21T15:01:11+00:00urn:sha1:ea5aa6993d4c906c1703563ddc304c324c4ae079
send a revised version of a proposal using the new in-replyto argument
suppliments existing 'root' tag with 'root-revision'
e 'reply' tag to the original proposal
feat(send): specify commits eg HEAD~22024-02-21T11:07:38+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-21T11:07:38+00:00urn:sha1:125ead4bb64d9e4a76266aabe5e826fc23551edc
specifiy commits or commit ranges in the
same way that `git format-patch` allows