Code changes
PhilaGroup/phila, tracked from 19 Jun 2026 (dev environment created). Built from real GitHub commits and deployments, not self-reported.
Estimated hours
Active time, capped per day
This month
Hours so far this month
Active days
Avg 10.2h per active day
Current streak
Consecutive active days
Commits
+2.3m / -309k lines
Deployments
2054 succeeded, 827 failed
DB changes
Schema / migration commits
Longest session
Longest unbroken stretch
How the effort splits across the four streams: the web application, commercialisation, the Android app, and the iOS app. Hours are apportioned by each stream’s share of the day’s commits and deployments.
Hours, commits, and deployments per contributor. Each person appears once, with all their GitHub accounts merged.
Total hours each completed and current month, per contributor. New months appear here as they begin, so you can look back over any period.
| Month | Pascal Radzilani | Matodzi | Total hours |
|---|---|---|---|
| August 2026 | 123h 12m | 105h 28m | 228h 40m |
| July 2026 | 281h 44m | 94h 34m | 376h 18m |
| June 2026 | 119h 4m | 12h 59m | 132h 3m |
Each box is a day. The number is hours worked; the colour shows how heavy the day was, green for a lighter day through to red for a grueling one. The thin bar under each day shows the stream mix. Click any day to see that day’s commits and deployments.
Total hours per weekday. Active about 6.4 days a week.
When in the day the work happens (by the hour, Africa/Johannesburg).
Most active: Evening (5pm-9pm)
Estimated active hours per day, capped at 16h.
The latest commits and deployments. Click any row to open it on GitHub.
Every commit and deployment carries a timestamp. Events within 90 minutes of each other are counted as continuous work; a larger gap is treated as a break, and each work session is credited 60 minutes for the ramp-up before its first commit. Any single day is capped at 16 hours so a long sprint never reads as implausible. This is the recognised git-hours method.
Treat this as a conservative floor. Research, design, debugging, planning, and meetings rarely produce commits, so real effort is higher than shown. Every number here traces back to commits and deployments that can be independently verified on GitHub.