tiennm99/awesome-ai-dev-tools
1
0 Fork 0
mirror of https://github.com/tiennm99/awesome-ai-dev-tools.git synced 2026-10-11 12:08:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: flag repos that stopped receiving pushes

Browse Source 
The maintenance criterion was unfalsifiable, so entries went years
without a push before anyone noticed by hand. The updater already
fetches pushedAt; warn when it is older than 90 days, alongside the
existing rename and archival annotations. Archived repos keep their own
warning rather than getting two.

Quantify the criterion in the README and CONTRIBUTING: dropped after 6
months idle, flagged past 3, with removal still a human decision.

Also correct two CONTRIBUTING claims the code contradicts — duplicates
are rejected by CI rather than ignored at run time, and renames do carry
history over once canonicalKeyMigrations has the old key.
This commit is contained in:
tiennm99 committed 2026-09-11 14:37:26 +07:00
1 parent 2e2ad56add
commit ce81c85645
4 files changed
+108 -7
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/CONTRIBUTING.md
+5 -3
View File
@@ -35,11 +35,13 @@ Optional fields: `notes` (for clarifications or caveats)
## Handling Duplicates and Changes
**Duplicate repos:** If a repo appears twice (same owner/repo), the second entry is ignored in the next daily run.
**Duplicate repos:** CI rejects them. `go run . -check` fails on a case-insensitive `owner/repo` match, so a duplicate never reaches a daily run.
**Renamed repos:** If a GitHub repo is renamed after being tracked, update the `repo` field in `data/agents.yml`. The updater will fetch fresh metadata under the new name. Historical data in `data/history.jsonl` remains under the old key and is not migrated.
**Renamed repos:** GitHub redirects the old slug, so the updater keeps working — it prints a `::warning::` naming the new slug. Update `owner`/`repo` in `data/agents.yml` to the new slug and add the old key to `canonicalKeyMigrations` in `history.go`, or the repo's star history detaches and its deltas show `—`.
**Deprecation:** To remove an agent, delete its entry from `data/agents.yml`. The next run will drop it from the README; historical data is preserved.
**Deprecation:** To remove an agent, delete its entry from `data/agents.yml`. The next run drops it from the README; its history stays in `data/history.jsonl`, so re-adding the entry later restores its star chart.
**Staleness:** An entry with no push in **6 months** is dropped. Past **3 months** the updater prints a `::warning::` naming the repo and its days idle, so the daily run surfaces candidates without anyone auditing the list by hand. Removal stays a human decision: a repo can go quiet between releases, and a historically significant one (`gpt-engineer`) is kept with a `notes` marker instead.
## PR Review