diff options
| author | DanConwayDev <DanConwayDev@protonmail.com> | 2024-12-03 15:29:06 +0000 |
|---|---|---|
| committer | DanConwayDev <DanConwayDev@protonmail.com> | 2024-12-03 15:29:06 +0000 |
| commit | d2478dbca6c5d3f61331ceabe20c6d9315cd6840 (patch) | |
| tree | 9cd79f52ac96378ef68b4798db48ee65839d9f74 /Cargo.lock | |
| parent | 79f55ad6488ddb628438580acf54a1d23a990cb3 (diff) | |
refactor: limit fetch to 1 trusted coordinate
previously fetch supported fetching multiple trusted coordinates at
once. The additional complexity trade off isn't worth it.
It will still fetch events related to the coordinates of maintainers
that the trusted maintainer lists.
A scenario where there might be multiple trusted coordinates is
where a large repo is split into multiple nostr repos to manage
pull requests and issues in seperate sub-units. I might therefore
have different remotes that target different identifiers.
There also might be different set of maintainers groups that are
have different views on the latest state of the same codebase and
they haven't split off into using different identifiers.
Its simplier ngit to fetch these different nostr repos independantly
when requested. git-remote-nostr will do this automatically as it
works through remotes but for ngit cmds a further change is required
so `get_repo_coordinates` and `try_and_get_repo_coordinates` prompts
to select the desired one.
Diffstat (limited to 'Cargo.lock')
0 files changed, 0 insertions, 0 deletions