A list of commits is not a picture of the week
Commit logs record what changed and lose what was being attempted. Forty commits across six branches tell a manager nothing, and tell the engineer who wrote them very little they still remember.
The useful unit is the piece of work, not the commit. Eleven commits on one branch fixing one defect are one line in a summary. A single commit touching a migration is three.
Grouping needs the branch, the pull request, and the linked issue to be read together, because any one alone misattributes the work. A branch name is often a guess, and a commit message is often "fix".
A weekly summary written this way is also the raw material for the release note, for the standup nobody wants to hold, and for the record of what a team actually spent its week on.
How the ActionFlow runs on the canvas
GitHub supplies commits, pull requests, and their linked issues for the period, read on a Start Scheduled trigger.
A Merge node joins them into a single record per piece of work, keyed by the pull request, with orphan commits kept in their own group rather than dropped.
A Loop node iterates over the work items. A Generate Text node writes each as a single line describing what was attempted and what landed.
A Text Classifier node assigns each item an area, the parts of the system your team names, so the summary groups the way your team thinks rather than the way the repository is laid out.
A Math node counts items and reviews per area, giving a manager a distribution without measuring anyone individually.
A Sort node orders areas by activity. A Generate Text node writes the opening paragraph from the grouped items rather than from the raw log.
A Slack node posts it to the team channel. A Notion node keeps the archive, which is what makes quarterly review a reading exercise rather than an archaeological one.
Nodes this ActionFlow uses
- Start Scheduled (Start): the weekly collection window.
- GitHub (Integration): commits, pull requests, and linked issues. Bitbucket fits the same slot.
- Merge (Control): one record per piece of work, keyed on the pull request.
- Loop (Control) with Generate Text (AI Core): one line per work item.
- Text Classifier (AI Custom): groups by the areas your team actually names.
- Math (Util) with Sort (Data): activity by area, ordered.
- Slack (Communication): posts the summary to the team channel.
- Notion (Integration): the archive that makes quarterly review readable.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.