Integration spotlight: GitHub

The GitHub integration is one of the first connectors we shipped, because for most engineering orgs, GitHub is the source of truth for what actually happened. Issues describe intent. PRs describe shipped reality. The gap between the two is where projects go wrong.

What we ingest

When you connect GitHub, StoryLens indexes:

• Repositories you have access to (read-only)
• Issues — title, body, labels, state, comments, linked PRs
• Pull requests — title, body, files changed, reviews, merge state
• Commits — message, author, timestamp, files touched

Everything is incremental. We watch webhooks and replay missed events on reconnect. You can scope to specific repos at any time.

What you can ask

Once it's indexed, the queries that used to take you 20 minutes of dashboard-flipping become one prompt:

• "What did the platform team merge last week, and which PRs are still in review?"
• "Which issues opened this sprint are still unassigned?"
• "Who's been merging the most fixes in the auth service this month?"
• "Summarize the discussion on PR #4823 — what's the open concern?"

The answers cite the underlying issues and PRs, so you can click through to verify.

Scheduled prompts

The real lift comes from scheduling. A "Friday eng update" prompt can pull a fresh week-over-week snapshot every Friday at 8am — no human in the loop, no Slack thread, no manual scraping. The result lands in your StoryLens dashboard and (if you want) your inbox.

Privacy

StoryLens never sees your code unless you ask it to. The default scope is metadata — issues, PR titles and descriptions, commit messages. If you want full diffs analyzed, that's an opt-in setting, and the diffs stay scoped to the queries you run.

That's it for the GitHub deep-dive. If you want to see this in action against your repos, book a demo. More integration spotlights soon.