What Firstweek reads from GitHub
- Repositories, pull requests, issues, and commit history
- Repository content and organization metadata
What shows up in the briefing
GitHub activity typically anchors the role-context and current-state sections - what's actively being worked on, recent architectural decisions, and who owns which part of the codebase.
Read-only, and nothing raw is ever stored
Every integration - GitHub included - connects read-only. Firstweek can never write to, modify, or delete anything in your tools. GitHub content is processed in memory and never persisted; only AI-generated summaries, and opt-in source snippets up to 200 characters, are saved.
Full detail: read the trust & security page for the complete data-handling policy, or the subprocessors list for exactly what GitHub data category is disclosed.
See what a real briefing built from sources like GitHub actually looks like.
See a sample briefing →