npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/sub_commands/send.rs, branch v1.0.0 Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.0.0 2024-02-29T13:00:02+00:00 feat(send): add proposal revision cli msg 2024-02-29T13:00:02+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-29T12:44:06+00:00 urn: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 master 2024-02-28T16:38:39+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-28T16:38:39+00:00 urn: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 feat(init): add customisation and defaults 2024-02-23T13:57:23+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-23T13:57:23+00:00 urn:sha1:d5284b758661c491e6a206570763f2982424b70a - allow more cli input options - allow customisation of more fields in interface - change default identifer from shorthand root commit to short name - defaults to existing repo event (users or other) or maintainers.yaml fix(push): remove force push bug 2024-02-23T12:25:11+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-23T12:25:11+00:00 urn:sha1:a9e4c6772a378fd28edbca9b9267d2e7d08bee2c introduced in b931b37e26486e4e6d15f302e87141dcf2f596ba refactor: remove confusing options, improve help 2024-02-23T10:12:54+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-23T10:12:54+00:00 urn:sha1:991da4d8dc2bbdd9832dd9252ebebc27d612154c from_branch and to_branch have been replaced by specifying revision ranges refactor: remove confusing options, improve help 2024-02-23T10:11:56+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-23T08:30:15+00:00 urn:sha1:b931b37e26486e4e6d15f302e87141dcf2f596ba from_branch and to_branch have been replaced by specifying revision ranges feat(push): add `--force` to issue revision 2024-02-23T08:15:24+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-23T08:15:24+00:00 urn:sha1:84d8f03cf2471d3530f4657055f272474880b6b5 wrapping `send --in-reply-to` unless branch up-to-date fix(list): support `--in-reply-to` latest revision 2024-02-22T10:11:39+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-22T10:11:39+00:00 urn:sha1:fdc15cb017b022a3b932ac5a337c649cb63df93c update list to support rebases via proposal revisions as created by `ngit send --in-reply-to` or upcoming change `ngit push --force` feat(send): in-reply-to arg for revised proposal 2024-02-21T15:01:11+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-21T15:01:11+00:00 urn: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~2 2024-02-21T11:07:38+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-02-21T11:07:38+00:00 urn:sha1:125ead4bb64d9e4a76266aabe5e826fc23551edc specifiy commits or commit ranges in the same way that `git format-patch` allows