Sectors / Software companies
Years of tickets, code reviews and design choices
Commit history, pull requests, bug reports and architecture docs show how real software is built and maintained. That record is what labs want. Client code and customer details can stay out.
Check my estimateWhat counts
The records that tend to matter
You decide which of these are included. Leaving any of them out is always an option.
Code reviews and pull requests
What reviewers spot, challenge and why.
Commit history and repositories
How a codebase grows, gets refactored and changes over years.
Bugs and tickets
How problems get reported, reproduced, prioritized and closed.
Design docs and release notes
The reasons behind how systems are built, and how they evolved.
What software firms ask first: code that belongs to clients
When you build software for clients, much of the code may be theirs. Who owns what is part of scoping, and client projects can be left out. You and your counsel decide whether a client's permission is needed.
Tickets and logs also mention your customers. In the de-identified copy, customer and developer names are replaced with placeholders, and any repo, tool or period can be excluded.
How it is handled
An NDA is in place from the start. Nobody asks for tokens or passwords. You approve a sample before anything goes out, and your repositories stay exactly where they are.
Two short questions
Do we have to include our core product?
No. Any repo or product you see as core can be held back.
Is our ticket history enough?
Often, yes. A well-kept issue tracker is a good starting point for the conversation.