Skip to content

binarythinktank/code_timing_from_commits

View on GitHub ↗Related repositories →

Simple script i created for myself to (very roughly) calculate the time i have spent on a project from the timing of my commits. This only kinda works if you have a frequent approach to committing. (Managers: this should not be used to measure developer productivity, its really not accurate enough for that)

active 2025-01-302025-01-30 (UTC)

Partial coverage25,194 / 26,319 hourly files (96%) · 2 absent upstream · 1,124 failed, retryable2023-08-152026-08-15 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
4
Pushes
2
Pull requests
0
Issues
0
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 1 days from 2025-01-30 to 2025-01-30. Pushes: 2 total, peak 2 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 0 total, peak 0 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
binarythinktank2200

Recent activity

Latest issues, pull requests and releases

No issue or PR events — this repo's activity is pushes only.

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.