npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/repo_ref.rs, branch v1.2.0

feat(init): support multiple git_servers

2024-04-08T15:10:05+00:00

in line with initial merged nip34 spec

update tag generation

2024-03-25T11:46:23+00:00

to reflect changes in rust-nostr

replace XOnlyPublicKey with wrapper PublicKey

2024-03-22T15:51:36+00:00

to reflect new name in rust-nostr

feat(init): add customisation and defaults

2024-02-23T13:57:23+00:00

- 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(repo-ref): filter for maintainer pubkey

2024-02-15T10:45:21+00:00

previously looking for p tag rather than author this kind of bug should be picked up by tests when our mock relay is applying filters before sending events

feat: find repo event by nevent or naddr

2024-02-14T16:44:56+00:00

if repo event cannot be found using unique commit the user can find it via a nevent or naddr also handle no PRs found

feat(repo_ref)!: align maintainers tag to nip34 style

2024-02-02T03:11:31+00:00

nip34 specifies that repo event tags with multiple values wuch as "relays" and "web" use theformat: `["tag", "item", "item"...]` instead of: ``` ["tag", "item"], ["tag", "item"], ``` this update also adds clarity. it is not obvious that using a p tag is intended to make the pubkey a co-maintainer. BREAKING CHANGE: format of maintainers tags in repo events has changed to reflect nip34 style and ngit will not detect the old format

feat(repo_ref)!: use nip34 kind and tags

2024-02-02T02:30:01+00:00

- change kind number - do not rely on d identifiers for unique commit id. set it as default to unique commit id shorthand. - remove "r-" prefix from unique commit id r tag and instead add checks for SHA1 validity - rename tag git_server to clone - add web tag - use single relays tag instead of multiple relay tags BREAKING CHANGE: change repo event kind and tags to reflect nip34 draft. events with the older kind will no longer be found and will not be in a valid format

chore: upgrade rust-nostr v0.27.0

2024-01-26T21:32:21+00:00

this is a contribution from jk (sectore) that I rebased and squashed into this commit. the tests were broken in the last few commits to rush out some fixes. this change may introduce more issues because of Relay.respond_standard_req.

feat(claim): change repo event kind

2024-01-22T00:00:00+00:00

so that it is outside the 30000 <= n < 40000 parameterized replacable range