Sample summaries
Honest by design
Git data says what changed, not what it means. Gitmayo keeps that evidence honest, then shapes its structure for the intended reader. These fictional demonstrations use separate product scenarios and reporting periods. They are not customer reports or production records.
Download each example as a PDF or PowerPoint. In the app, your saved report is ready to copy or export. Outside recipients require review by default; you control Review before sending.
Fictional demonstration for a client
Client reportCheckout reached production on 16 July; billing and accessibility fixes were merged, while onboarding and team invites remain in progress.
Deployed
- Stripe checkout: a successful production deployment of the payment flow was recorded on 16 July, after the checkout change was merged on 15 July.
Merged
- Annual billing: a correction to annual-plan totals was merged on 15 July. The evidence does not record what caused the wrong total.
- Plan selector: clearer validation and keyboard focus states for the plan selector were merged on 16 July.
In progress
- Onboarding: the new onboarding flow has been open as a pull request since 14 July and is not yet merged.
- Team invites: team-invite work has commits outside the default branch, last recorded on 17 July, so it is not presented as released or deployed.
Repository activity
- Maintenance: dependency updates and test changes reached the default branch between 14 and 18 July. No release or deployment evidence was observed for that work.
Failed / unknown
- A preview deployment for the onboarding branch failed on 17 July. The branch remains in progress.
Heads-up
- Owner-provided context: review the mobile settings layout before the next release.
- Owner-provided context: confirm annual-plan totals in the next billing review.
Why it reads this way: This fictional scenario assumes explicit successful production deployment evidence for the payment flow. It is not evidence of a Gitmayo customer deployment.
Fictional demonstration for an executive
Executive reportCheckout reached production on 16 July; billing and accessibility fixes were merged, while two workstreams remain in progress.
Delivery state
- Stripe checkout: a successful production deployment was recorded on 16 July.
- Billing and plan selector: the annual-plan total correction and the plan-selector accessibility changes were merged on 15 and 16 July; no deployment evidence was observed for them.
- Onboarding and team invites: onboarding has an open pull request from 14 July, and team-invite commits remain outside the default branch as of 17 July.
- Maintenance: dependency and test updates reached the default branch without release or deployment evidence.
Risks, blockers and missing evidence
- A preview deployment for onboarding failed on 17 July, so that work remains in progress.
- The evidence does not record why the annual-plan total was wrong; that context would have to come from the owner.
- Owner-provided context: review the mobile settings layout before the next release and confirm annual-plan totals in the next billing review.
Why it reads this way: The same fictional facts are compressed into delivery state and attention items; merged work is not presented as deployed.
Fictional demonstration for an investor or board
Investor or board reportInvestor or board report
Built
Report export retry: The retry flow was merged. Previously, report owners had to restart preparation after an interrupted export. The change is intended to preserve their draft so they can finish preparing a board update. Customer availability is not established by the merge.
Measurement: Not measured in the supplied evidence. No product or business outcome is established for this change.
Fixed
Board attachments: A correction for missing report attachments was merged. It is intended to retain the selected report when an owner prepares a board pack. Release and production availability are not confirmed.
Measurement: Not measured in the supplied evidence. No product or business outcome is established for this change.
This example and its evidence are fictional. Intended benefits are not measured outcomes.
all claims come from github data gathered from 2026-10-12T00:00:00.000Z to 2026-10-19T00:00:00.000Z (end exclusive).
Why it reads this way: This independent fictional reporting-product scenario uses current product stories. Each change keeps its merged state and missing measurement; no customer availability or outcome is claimed.
Fictional demonstration for an internal stakeholder
Internal stakeholder reportCheckout deployed successfully on 16 July; billing merged, with onboarding and team invites still moving.
Delivery and work in progress
- Stripe checkout: a successful production deployment was recorded on 16 July.
- Billing: the annual-plan total correction was merged on 15 July; no deployment evidence was observed for it.
- Plan selector: validation and keyboard focus changes were merged on 16 July.
- Onboarding: an open pull request from 14 July, not yet merged.
- Team invites: commits outside the default branch, last recorded on 17 July.
- Maintenance: dependency and test updates landed on the default branch without release evidence.
Decisions and handoffs
- The onboarding preview deployment failed on 17 July and needs another attempt.
- Owner-provided context: review the mobile settings layout before the next release.
- Owner-provided context: confirm annual-plan totals in the next billing review.
Why it reads this way: The same fictional facts are expanded into implementation states without turning branch activity into shipped work.
Create your own report
Connect GitHub, choose the reader, and Gitmayo writes your first plain-English report.