weekly-report
Weekly Report
Turn a week of commits on one branch into a report a team lead can act on: what was worked on, what changed per country, where the risk is, and who to credit.
Arguments: a branch name, and either a starting commit ref or a date. Both required — ask for whichever is missing rather than guessing. The window runs from that ref/date to HEAD of the branch as of now.
Commit grammar: #<issue number>: <Country> - <message>.
The report is built from dossiers — one fixed-shape record per issue, compiled from that issue's full diff. Everything downstream reads dossiers, never raw diffs. That is what keeps a 40-commit week and a 400-commit week producing the same report.
1. Resolve the window
Fetch the branch, then pin both ends of the window:
- Start: the given ref, or the first commit on or after the given date.
- End: current
HEADof the branch.
Record both full SHAs and their dates. Fail loudly if the branch or ref does not exist — never fall back to the current branch.