GitHub + Go Fig
Connect GitHub to Go Fig for engineering effort tracking and R&D capitalization.
Engineering is often the largest cost center and the hardest to allocate. Go Fig's GitHub integration pulls commits, pull requests, reviews, and repo activity at the contributor grain and joins them into the Financial Intelligence Graph alongside Jira, HRIS, and payroll. That join is where R&D capitalization becomes defensible: a commit links to a Jira issue, the Jira issue carries the capitalization-eligible flag, the contributor links to a loaded cost rate from payroll, and the resulting capex-vs-opex split traces every dollar back to specific code that shipped. Beyond capitalization, engineering managers get contributor-level velocity and review throughput without standing up a separate productivity tool, and finance gets a read on which product areas are absorbing engineering effort. Bot commits are filtered, monorepos are handled with per-path attribution, and the integration respects GitHub's fine-grained permission model so only the repos you explicitly scope are visible.
Key facts
- Auth
- GitHub App install, fine-grained permissions
- Scope
- Per-repo or org-wide
- Grain
- Commit, PR, review, contributor
- Monorepo
- Per-path attribution supported
- Sync cadence
- Webhook-driven, near real time
What you can do with GitHub data in Go Fig
R&D Capitalization
Join commits and PRs to Jira capitalization flags and loaded engineer costs to produce an auditable capex-vs-opex split every month.
Engineering Effort Allocation
Attribute engineering cost to products, initiatives, or repos using contributor-level activity rather than manual percentage estimates.
Velocity and Throughput
Track PR throughput, review latency, and contributor load alongside financial investment so capacity discussions are data-backed.
Data available from GitHub
Go Fig extracts and normalizes the following data from your GitHub account:
How to connect GitHub
Install the Go Fig GitHub App
From your GitHub organization settings, install the Go Fig GitHub App. During install, pick either all repos (simplest for org-wide attribution) or a subset (most common for mixed public/private orgs where only internal repos should be in scope). Fine-grained permissions mean Go Fig only gets read access to the scopes it needs.
Pick private vs public and the scope model
Most finance use cases need private repos only; open-source contribution data is noisier. You can also exclude repos that are bot-heavy (infra, dependency-update mirrors) at this step. Monorepo shops can declare per-path ownership so commits are attributed to the right product area.
Map contributors to payroll identities
GitHub usernames are matched to your HRIS records by email. Unmatched contributors (contractors, former employees still in history, bots) are flagged for explicit mapping or exclusion. This matching is what enables loaded-cost multiplication downstream.
Join to Jira and payroll
Connect Jira (commit messages and PR titles are scanned for issue keys) and your HRIS or payroll connector. Go Fig builds the R&D capitalization starter flow: commits × loaded rate × capitalization-eligible-flag from Jira, aggregated by month, initiative, and GL account. Most controllers wire this directly into close.
Authentication: GitHub App installation with fine-grained permissions. Read-only scopes on Contents, Metadata, Pull Requests, and Issues are required; write scopes are never requested. Installation is per-repo or org-wide, and the app can be uninstalled from GitHub Settings at any time without touching Go Fig.
Common Questions About GitHub Integration
How does Go Fig handle monorepos?
Per-path attribution. You declare which directory trees belong to which product or initiative (for example /apps/billing is billing, /apps/analytics is analytics, /packages/shared is shared infra). Commits touching multiple trees are split proportionally by lines-changed, with an override available when proportional is not the right model (infrastructure-refactor PRs, for instance, are often better attributed to shared infra in full).
How are bot commits and automated PRs filtered?
Commits from GitHub Apps, Dependabot, Renovate, and any user ending in [bot] are excluded by default from effort metrics and capitalization flows but retained in the raw data for auditability. You can also exclude specific human users (for example, a release-automation service account) or entire repos (infra mirrors) from cost attribution in the connector settings.
Can R&D capitalization be flagged via Jira labels or GitHub labels?
Both. The default model uses Jira labels or a custom field on the issue because Jira is usually where the business decision lives (feature vs maintenance, capitalizable initiative vs not). For teams that run capitalization decisions from GitHub directly, PR labels work too. The flow can also combine both, labels from either source flag a PR as capex-eligible.
Does Go Fig join GitHub PR throughput to Jira issues?
Yes. Commit messages and PR titles are scanned for Jira issue keys (configurable pattern, default ABC-123 style). The resulting join lets finance roll up engineering effort by Jira epic, sprint, or initiative, which is usually the grain business partners actually care about. Orphan commits without a Jira reference are bucketed to an 'unattributed' pool so you can see how much work escapes the ticketing system.
Is GitHub Enterprise Server supported in addition to GitHub.com?
Yes. GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server are all supported. Enterprise Server customers provide the base URL and a GitHub App configured on their server; the data model downstream is identical. Go Fig respects audit-log requirements so the security team sees every read the integration performs.
Related Engineering integrations
Other systems Go Fig connects into the Financial Intelligence Graph, often alongside GitHub.
Ready to connect GitHub?
See how your GitHub data looks in Go Fig with a personalized demo.
Book a Demo