How does diffbill integrate with GitHub?
How it works
diffbill reads your GitHub repositories to capture merged pull requests as billing records. It uses PR titles, descriptions, linked issues, and diff summaries to generate professional invoice line items — replacing manual tracking with your actual shipping history.
Setup and workflow
Authorize diffbill with your GitHub account via OAuth.
Select the repository and date range you want to bill for.
diffbill fetches all merged pull requests in that window.
Linked issues add business context to each line item.
AI rewrites technical PR context into client-facing descriptions.
Review, edit, and exclude before creating a Stripe draft invoice.
What you get
Every merged PR is captured
No more forgotten work. Your complete shipping history becomes a searchable billing record.
Retroactive billing from Git history
Invoice any past date range. If the code was merged, you can bill for it — even months later.
Linked issues add context
Issue titles and descriptions provide the business context that makes invoice descriptions richer.
Source-linked evidence
Pro and Team plans attach clickable PR references so clients can verify delivered work.
Common questions
Does diffbill read my source code?
No. diffbill reads PR metadata, titles, descriptions, linked issues, and short diff excerpts. It does not clone your repository or access full source files.
Does diffbill work with private repositories?
Yes. After GitHub OAuth authorization, diffbill can access both public and private repositories that you grant access to. You can revoke access at any time.
Can I use multiple GitHub repositories?
Yes. Pro and Team plans support multi-repo billing. The Starter plan is limited to one repository.