Does git history matter? Why commit history is worth more than a code snapshot

Does git history matter for a data license?

Yes. A code snapshot shows what the software is today; git history shows how it got there. Commits, pull requests, review comments and merge decisions record each change, who proposed it, who questioned it and why it was accepted or reversed. For AI developers training and evaluating coding agents, that sequence is closer to real engineering work than any single version of a repository.

A fractional chief technology officer (CTO) often sees the moment this history is at risk: a platform move, a monorepo consolidation, a squash-and-import, or an acquisition clean-up. Each can flatten years of commits into a single "initial import."

This page explains what history adds, what to preserve before a migration, and how to raise it with a company before introducing it to SourceX.

What does history hold that a snapshot cannot?

The key pairing is change plus reason plus outcome. A snapshot cannot supply any of the three. The same logic makes test suites linked to the changes they verify valuable, since a test is an objective check on a change.

When is history most at risk?

Raise the point when a technical event is already scheduled.

If the history is already gone, say so; the company may still qualify through other systems. The question is what exists today and who can export it.

What to preserve before a migration

A short sequence works for most engineering teams:

1. Take a full mirror clone of each repository, including all branches and tags, before any rewrite.
2. Export pull request and review data from the hosting platform using its documented export or API, and store the output next to the mirror.
3. Archive the issue tracker and its links to commits, since references are what connect the change to its reason.
4. Archive CI logs or at least the pass-fail results for released versions.
5. Record who owns each archive and where it lives, so an inventory can list it later.
6. Keep the old platform account alive until the export is verified, not just requested.

None of this requires giving a copy to anyone outside the company. A company can list these archives as systems and years of history with the data inventory builder, which helps list systems without sharing code.

Common mistakes

What rights questions apply to code history?

Code history contains more than the company's own code. Check:

• Contributor agreements: did employees and contractors assign their work to the company?
• Client-owned work: agency and consulting repositories often belong to the client.
• Open-source components: license terms attach to the code that was included.
• Secrets and personal data embedded in commits or comments, which need removal or redaction.
• Customer data accidentally committed in test fixtures.

A company that mainly writes code for clients without consent is a red flag. A product company with its own repositories, a long history and clear assignments is a strong candidate. The PII redaction matrix helps frame what needs removing from embedded data.

What to say to a CTO or founder

How the introduction works

You introduce; the company and SourceX run the rest. You never see or hold code.

1. Register and send the founder or CTO your referral link, or use the referral form.
2. The company applies and SourceX checks headcount, repository age, system breadth and rights.
3. The company inventories repositories, review tools, trackers and CI, with the years each covers.
4. One all-in price and the license terms are agreed before any buyer review.
5. Once the company is deal-ready, buyers typically respond within about two weeks.
6. After signature, secrets and personal data are redacted under the agreed rules and the data is delivered.
7. The company is paid; your reward follows after SourceX receives its fee.

How rewards work for a fractional CTO

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The reward is a share of SourceX's fee and does not reduce the company's price. Check your client agreements for any disclosure requirement before registering. More on the role is at referral opportunities for fractional CTOs.

When it is not worth raising

Skip it for a company under the size baseline, a team that writes only client-owned code, or one that has already licensed the same code history for AI training. Related record types like PSA ticket histories fit better when the client is a managed service provider rather than a software product firm.

Next step

Ask one client whether the full commit and review history will survive their next platform change. If it will and they might consider a license, register as a partner, or have the sponsor apply at sourcex.si/apply.