npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/sub_commands/push.rs, branch v1.3-beta1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.3-beta12024-07-05T10:06:04+00:00feat(init): group by status2024-07-05T10:06:04+00:00DanConwayDevDanConwayDev@protonmail.com2024-07-05T10:06:04+00:00urn:sha1:ba82a894fad645757c49242c11573b6c5dd8d1e6
show open proposal by defult and include options to filter
by other statuses
there are not tests for this currently as the intention is
to transform 'list' further by adding a 'fetch'
feat(login): login with nip46 remote signer2024-06-28T14:16:43+00:00DanConwayDevDanConwayDev@protonmail.com2024-06-28T14:16:43+00:00urn:sha1:a82546b70303000b4fc053a1ee21d3d8c7d6ad66
and save details in git config
refactor: replace keys with signer2024-06-25T08:06:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-06-25T08:06:47+00:00urn:sha1:b63bfc9a34657c5767c507deb7c059e24dd22779
so that nip46 bunker signing can be added
feat(login): store in git config and use cache2024-06-24T08:39:18+00:00DanConwayDevDanConwayDev@protonmail.com2024-06-24T08:39:18+00:00urn:sha1:173ab188b326fbe78cfba4ab455a74619f4556bb
replace ngit yaml file config with:
* nsec / ncryptsec / npub in git config in nostr.* namespace
* sql database cache for metadata and relay events
allow different logins to be used for different git repositories by
storing login in local git config
feat(send): `in-reply-to` tags npubs and events2024-05-07T08:10:33+00:00DanConwayDevDanConwayDev@protonmail.com2024-04-22T06:26:15+00:00urn:sha1:10498b953d36304b441fcb162155c2487046206f
in addition to being used to create a new proposal revision,
in-reply-to can now be used to reference other events and npubs.
for example an issues or kind 1 threads where the proposal is relevant
the proposal will only be marked as a revision if the first parameter is
a reference to an existing proposal root
use Sha1Hashin new location2024-03-22T15:51:31+00:00DanConwayDevDanConwayDev@protonmail.com2024-03-22T15:51:31+00:00urn:sha1:f7d520e9ccb6084144a3e963516e40a322add0c8
it had moved from 'prelude' to 'hashes'
feat(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