# Sample repo snapshot: Tally, 1 to 14 August

A fictional result of the Repo snapshot recipe: what shipped in two weeks, grouped by area, with the settings that changed and what needs doing.

> [!info]
> **Fictional example.** Tally and the Fernbrook team are invented. This shows the shape of what the *Repo snapshot* recipe produces from git and GitHub.

<!-- onecell:block {"type":"stats","items":[{"note":"pull requests","label":"Merged","value":"23"},{"label":"Contributors","value":"4"},{"note":"both run on deploy","label":"Migrations","value":"2"},{"note":"2 waiting on review","label":"Open pull requests","value":"5"}]} -->
| Metric | Value | Change |
| --- | --- | --- |
| Merged | 23 |  |
| Contributors | 4 |  |
| Migrations | 2 |  |
| Open pull requests | 5 |  |

## Shipped, by area

| Area | What changed |
| --- | --- |
| Invoices | Partial payments; invoice PDFs in the client's language |
| Payments | Bank transfers in euros via Stripe; clearer failed-payment emails |
| Reminders | The job-queue version, behind a flag and off in production |
| Settings | Two-factor sign-in for every account |
| Fixes | Rounding on invoices with more than 20 lines; the CSV export date format |

## Settings and operations

- New setting `REMINDERS_QUEUE`, off by default. Turn it on only after the dry run.
- Stripe webhook now also listens for `payment_intent.processing`; update the endpoint in the Stripe dashboard.

## Needs doing

- [ ] Review the two pull requests waiting more than three days
- [ ] Write the release note for partial payments
- [ ] Record the decision behind the fourth retry on annual plans