tiennm99 724990af1d feat: let commits-per-repo 0 mean every commit ...

The pagination guard broke on seen >= maxPerRepo, so a cap of 0 stopped
before the first page and rendered empty productive-time,
productive-weekday and most-commit-language cards. That inverted the
meaning 0 carries for top-repos, where it already means unlimited.

Treat a cap of 0 or less as no cap. Verified against a real repo: a cap
of 100 still stops at 100, while 500 and 0 both walk the full 382-commit
history.

2026-08-13 14:19:41 +07:00

..

code-standards.md

docs: focus each file on users or coworkers, drop unrelated content (#18)

2026-04-19 10:34:02 +07:00

codebase-summary.md

feat(card): configurable start of week (#25)

2026-04-21 20:57:21 +07:00

deployment-guide.md

feat(card): configurable start of week (#25)

2026-04-21 20:57:21 +07:00

design-guidelines.md

feat(card): configurable start of week (#25)

2026-04-21 20:57:21 +07:00

project-overview-pdr.md

docs: focus each file on users or coworkers, drop unrelated content (#18)

2026-04-19 10:34:02 +07:00

project-roadmap.md

docs: focus each file on users or coworkers, drop unrelated content (#18)

2026-04-19 10:34:02 +07:00

system-architecture.md

feat: let commits-per-repo 0 mean every commit

2026-08-13 14:19:41 +07:00