Accepted delivery consistency
Track a shipping rhythm that opens back to accepted work.
Ship Streaks counts days with accepted, nonzero-value delivery and lets the developer or organization inspect the evidence behind every point in the chain.
Calendar-day and configured-workday views stay separate, so weekends, work schedules, and inactive periods are not quietly collapsed into one headline number.
Consistency is useful context. It should never become a proxy for hours worked.
A ship day requires accepted work with measured value. The streak can motivate a builder and help a team understand continuity, but it does not grade code quality, effort, availability, seniority, or the importance of work that Git cannot observe.
The result is only useful if you can see what produced it.
Accepted ship days
Counts a day only when qualifying work reaches the tracked branch and carries nonzero accepted value.
Calendar-day chain
Shows consecutive qualifying dates without pretending that this schedule fits every person or team.
Configured-workday chain
Uses the selected workweek so non-working days do not silently break or extend the intended streak.
Current and best streaks
Separates the active chain from the best historical chain across quarter, six-month, year, and lifetime views.
Underlying accepted work
Lets the reader open the repository and contribution evidence that qualified each date.
Share controls
Supports private work as approved aggregates without exposing repository, client, or contribution details by default.
From repository evidence to a readable record.
Select the tracked repositories
Connect the repositories and identities whose accepted work can qualify a personal or team ship day.
Apply the chosen schedule
Calculate calendar-day and configured-workday chains independently from the same accepted delivery ledger.
Open and share the evidence
Inspect qualifying work, change the time window, and share only the streak record and context you choose.
One evidence base, read from the right perspective.
See your delivery rhythm without reducing work to commits.
Use the streak as a personal continuity record and open the accepted contributions that created it.
- Calendar and workday modes
- Quarter through lifetime history
- Milestone sharing controls
Understand continuity without enforcing performative activity.
Use team chains as an operating rhythm signal alongside accepted value, coverage, leave, role, and work the repository cannot capture.
- Team and contributor views
- Repository-backed qualification
- Schedule and leave context
Clear evidence boundaries are part of the product.
A qualifying ship day does not establish how many hours someone worked or whether they were available on non-qualifying days.
A longer streak is not proof of greater output, quality, impact, or employee performance.
Leave, discovery, planning, mentorship, customer work, incidents, and long-running changes can interrupt a repository streak without indicating a problem.
Questions
What a Ship Streak can and cannot tell you.
A streak describes accepted delivery continuity. It does not describe every kind of work or every reason for a break.
What qualifies as a ship day?
A day qualifies when work reaches the tracked branch and carries nonzero accepted value. Raw commits, local activity, generated output, and changes without accepted value do not create a ship day by themselves.
Why are calendar and workday streaks separate?
A calendar streak treats every date as consecutive. A configured-workday streak follows the selected workweek so normal non-working days do not silently break or extend the intended chain.
Does a longer streak mean higher productivity?
No. A streak does not establish hours worked, code quality, business impact, seniority, or employee performance. It is one continuity signal that should be read beside accepted value and work context.
What can explain a break in the streak?
Leave, planning, discovery, mentorship, customer work, incident response, long-running changes, repository access, and role differences can all create a gap without indicating a delivery problem.
Make the streak evidence-based
Track consistency without rewarding commit noise.
Connect your repositories and let accepted, nonzero-value work define each ship day.