truelo + GitHub
truelo reads your team's GitHub activity — commits and pull requests — and turns it into a readable end-of-day summary, so updates reflect what was actually built instead of what someone remembered to type.
What you get
Commits and PRs become a summary
truelo groups the day's GitHub activity per person and writes a clear recap, so nobody has to narrate their own work.
Effort from what changed, not how many lines
The effort estimate is content-based — drawn from what changed, the tickets touched and reviews — and folds in self-reported non-code work. There's no lines-of-code ranking.
Connect once, at the org level
You link GitHub for the organization a single time; each team's data stays its own and encrypted.
Fair by design
Everyone can open their own numbers, and there's no stack-ranking of who committed the most.
How it works
- 1
Add truelo to Slack.
- 2
Connect your GitHub organization once.
- 3
Run /wrap — the summary now includes your GitHub activity.
GitHub integration — FAQ
What GitHub data does truelo use?
Commits and pull requests, to ground each day's summary and the content-based effort estimate — combined with Jira activity when connected.
Does truelo rank developers by lines of code?
No. Effort is content-based, estimated from what changed rather than line counts, and there's no stack-ranking — everyone sees their own numbers.
What permissions does the GitHub connection need?
truelo uses your GitHub activity (commits and pull requests) to build summaries. For the exact scopes it requests, review the permission screen shown when you link GitHub.
Do we have to use GitHub?
No. GitHub is optional — it makes summaries automatic. You can still run /wrap manually and use time off without it.