even if the repo event doesn't exist there may be many issues
and proposal that reference it so it makes sence to:
1. show the repo Menu with a count of proposals and issues
2. show the details within the address point
2. show the issues and proposals page with a warning
RepoPageWrapper stops overwriting all content with error
RepoHeader show warning
RepoDetails show basic details from address point and a warning
and link to it whenever the UserHeader is displayed.
closes issue:
nostr:nevent1qqsyxwvgdaacc3hcd9rjwmjwqsfpu8guhrj37026ntl3aqw02mrprsgpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgq3ql5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqseukj7u
and partially fulfills issue:
nostr:nevent1qqsyxwvgdaacc3hcd9rjwmjwqsfpu8guhrj37026ntl3aqw02mrprsgpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgq3ql5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqseukj7u
choose repo events based from earliest_unique_commit and indentifier
based on:
- number of mentions (issues and root patches)
- most recent created_at
identify repo events for the same repository based on identical identifiers
and use of earliest_unique_commit
use stores for collections of repo events
- update repo event tags to reflect nip34
- refactor: move RepoSummary interface and default into type.ts
the notable visible change is to use `clone` tag in place of
`git_server`
non-nip34 tags are supported: `unique_commit` and `maintainers`.
these enable desirable functionality to be maintained.
DanConwayDev
jk