npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/sub_commands/push.rs, branch v1.1.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.1.02024-03-08T17:27:13+00:00feat(send): compare against origin/main vs main2024-03-08T17:27:13+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-08T16:49:03+00:00urn:sha1:098b0258fdd581c750099cb463adbddb57843388
catch more errors when proposed commits
are not connected to origin/main branch
improve default selected commits when on main branch
feat(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
feat(init): add customisation and defaults2024-02-23T13:57:23+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-23T13:57:23+00:00urn: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
refactor: remove confusing options, improve help2024-02-23T10:12:54+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-23T10:12:54+00:00urn:sha1:991da4d8dc2bbdd9832dd9252ebebc27d612154c
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
fix(list): support `--in-reply-to` latest revision2024-02-22T10:11:39+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-22T10:11:39+00:00urn: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 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
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.
refactor: remove reliance on 'commit' tag2024-02-16T20:41:59+00:00DanConwayDevDanConwayDev@protonmail.com2024-02-16T20:41:59+00:00urn:sha1:a645273433fe3a716dd9c43ad9276da066af6127
as part of nip34 compliance