Heatmap
- Bright bars
- Push or timely merge to trunk
- Dim bars
- Stale merge (branch open 24h+ before merging)
- Faint bars
- Branch open but no push or merge that day
- Gaps
- No integration activity that day
- Cyan bars
- Weekends and holidays
Traffic light
- Green
- Under threshold
- Amber
- No push for 24h+
- Red
- Over threshold
Jul 4
Sep 25
3 over threshold
You are not doing CI.
0
over 24h
2
repos
3
open
92
pushes
0
merges
6h
P90
Jul 4
Sep 25
feature/reviews
62h
feature/stock-indicator
37h
59 trunk pushes
0 merges
P90 6h
Threshold
24h
Jul 4
Sep 25
feature/order-summary
50h
33 trunk pushes
0 merges
P90 3h
Threshold
24h
The signal is only as honest as the team behind it.
You can cheat this. Here's how.
- Delete branches without merging. The monitor marks them as abandoned. The team sees every deletion.
- Work locally and push directly to trunk. The monitor cannot see local branches. If you are integrating to trunk multiple times a day, you are doing CI whether the monitor sees it or not. If you stop pushing for 24+ business hours, the monitor goes amber.
- Rename a branch to reset the clock. The monitor tracks branches by name. A rename gives you a fresh timer, but the effort could have been spent integrating.
- Mark everything as a spike. The team sees every spike. If a spike is later merged, the monitor flags it with a warning.
- Create fast branches to dilute the metrics. The monitor uses "over 24h" count and P90 instead of an average. Quick branches do not reduce these numbers.