npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/tests/send.rs, branch v1.0.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.0.02024-02-29T13:00:02+00:00feat(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
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