repo_info table could probably use a view to show the lastest info for each repo
Open
database
- Dominant language
- Python
- Stars
- 13
- Forks
- 17
- Avg merge
- 6h 59m
- Merged PRs (30d)
- 1
Description
It seems like `repo_info` is a historical log of things like watchers/stars/open issues and prs etc.
For usecases like getting the current security.md/changelog/etc it may be helpful to have a view that reduces the table to just one row per repo for the latest run.
Contributor guide
Assessment
This issue has not been assessed yet.