@@ -0,0 +1,25 @@
1+---
2+id: 1042
3+title: how do we add new remotes
4+type: chore
5+status: review
6+priority: p2
7+created: 2026-11-08T06:26:18Z
8+updated: 2026-11-08T06:27:05Z
9+source: human
10+moves: 2026-11-08T06:26:22Z inbox doing drag; 2026-11-08T06:27:05Z doing review agent
11+area: import
12+---
13+
14+
15+## Notes
16+
17+- 2026-11-08 06:27Z (agent): Answer: add the repo's https clone URL as a line in sources.txt, then run make import, make index and make build (or make serve, which builds first). No code change is needed.
18+ - make import: makes a bare mirror of each URL in repos/ (git clone --mirror for a new one, git fetch --prune for the rest), then fetches description and fork flags from the host's API into data/meta.json.
19+ - make index: reads repos/ and overrides.txt into data/projects.json. The project's name is the repo name.
20+ - make build: renders public/.
21+ Limits I found in internal/store/meta.go:
22+ - Only github.com and gitlab.com have an API entry. A URL on any other host (Codeberg, sr.ht, a local path) makes import stop with "no API for <host>" after mirroring. That is why 1041 (this repo, which has no remote) needs code.
23+ - Each owner's API list is read with per_page=100 and no paging. That's fine today (44 sacenox, 44 xonecas, 17 gitlab), but an owner with more than 100 repos would get no description for the rest.
24+ If the same project lives on two hosts, add 'merge <url> <url>' to overrides.txt; hide, rename and tag rules go there too.
25+ Nothing was changed: I read the Makefile, cmd/site/main.go and internal/store.