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.

1 files changed, 16 insertions, 7 deletions

diff --git a/src/lib/repo_ref.rs b/src/lib/repo_ref.rs
index 69fbe64..988c87d 100644
--- a/src/lib/repo_ref.rs
+++ b/src/lib/repo_ref.rs
@@ -188,6 +188,13 @@ impl RepoRef {
     /// coordinates without relay hints
     pub fn coordinates(&self) -> HashSet<Coordinate> {
         let mut res = HashSet::new();
+        res.insert(Coordinate {
+            kind: Kind::GitRepoAnnouncement,
+            public_key: self.trusted_maintainer,
+            identifier: self.identifier.clone(),
+            relays: vec![],
+        });
+
         for m in &self.maintainers {
             res.insert(Coordinate {
                 kind: Kind::GitRepoAnnouncement,
@@ -226,7 +233,7 @@ impl RepoRef {
             "{}",
             NostrUrlDecoded {
                 original_string: String::new(),
-                coordinates: HashSet::from_iter(vec![self.coordinate_with_hint()]),
+                coordinate: self.coordinate_with_hint(),
                 protocol: None,
                 user: None,
             }
@@ -238,7 +245,7 @@ pub async fn get_repo_coordinates(
     git_repo: &Repo,
     #[cfg(test)] client: &crate::client::MockConnect,
     #[cfg(not(test))] client: &Client,
-) -> Result<HashSet<Coordinate>> {
+) -> Result<Coordinate> {
     try_and_get_repo_coordinates(git_repo, client, true).await
 }
 
@@ -247,7 +254,7 @@ pub async fn try_and_get_repo_coordinates(
     #[cfg(test)] client: &crate::client::MockConnect,
     #[cfg(not(test))] client: &Client,
     prompt_user: bool,
-) -> Result<HashSet<Coordinate>> {
+) -> Result<Coordinate> {
     let mut repo_coordinates = get_repo_coordinates_from_git_config(git_repo)?;
 
     if repo_coordinates.is_empty() {
@@ -265,7 +272,11 @@ pub async fn try_and_get_repo_coordinates(
             bail!("couldn't find repo coordinates in git config nostr.repo or in maintainers.yaml");
         }
     }
-    Ok(repo_coordinates)
+    Ok(repo_coordinates
+        .iter()
+        .next()
+        .context("would have bailed if no coordinates found")?
+        .clone())
 }
 
 fn get_repo_coordinates_from_git_config(git_repo: &Repo) -> Result<HashSet<Coordinate>> {
@@ -285,9 +296,7 @@ fn get_repo_coordinates_from_nostr_remotes(git_repo: &Repo) -> Result<HashSet<Co
     for remote_name in git_repo.git_repo.remotes()?.iter().flatten() {
         if let Some(remote_url) = git_repo.git_repo.find_remote(remote_name)?.url() {
             if let Ok(nostr_url_decoded) = NostrUrlDecoded::from_str(remote_url) {
-                for c in nostr_url_decoded.coordinates {
-                    repo_coordinates.insert(c);
-                }
+                repo_coordinates.insert(nostr_url_decoded.coordinate);
             }
         }
     }