Details

Browse code changes, explore activity, and understand when history updates.

What you can do

  • Browse commits by day, week, month, year, or all history.
  • Jump to the latest period or step backward and forward through history.
  • Filter by change type and search commit messages or hashes.
  • Compare matching commits, active periods, and the busiest hour or day.
  • Hover or focus chart bars for counts, and select them to drill down from a week, month, year, or all-history view.
  • See all-history insights above the filters: commits per active day, the busiest day, the longest streak, the share made after midnight, a 12-month change-type mix, the most-touched areas, and a weekday-by-time rhythm. Each chart has a table view.
  • Start with 10 timeline entries, load 10 more at a time, and share the current filters through the page URL.
  • Read curated weekly highlights on the Changelog page. The newest three months start open, older months fold away, and each month shows its commit count and change-type mix.

What to know

  • History is uploaded from Git after checks pass on pushes to main.
  • History and API responses use five-minute caches.
  • Expired data refreshes when requested, so cached responses can temporarily lag behind an import.
  • The homepage total and explorer can temporarily differ because their caches refresh separately.
  • Failed refreshes can retain older data; failed fresh API reads return an error that can be retried.

Reading the activity

  • Dates and hourly buckets use Jakarta time (WIB).
  • Daily views show active hours and the peak hour; wider ranges show active days and the busiest day.
  • Charts and summary totals include every matching commit, even when only 10 timeline entries are visible.
  • Counts describe recorded commits, not the size or effort of each change.
  • Messages without a recognized commit prefix appear under Other.
  • Insights ignore the filters. Areas come from the scope in subjects like feat(Timer), so commits without one are not counted, and differences in capitalization are merged.
  • The weekly changelog combines curated summaries with newer commit subjects.

How it works

Git history is imported into a separate database, then cached on the server. Your selected filters determine the summaries, chart, and timeline; changing them updates the URL and requests matching results.

Commit history data flow diagram
Rendering diagram…

Changelog

Messages mentioning Commits or its components, oldest first; dates and times use Jakarta time (WIB).

Loading change history…