Industries / Software teams
How your team really builds and ships
Review threads, pull requests, tickets and architecture docs show software being built and maintained over years. That is the record labs want. Client code and customer details can be excluded.
Check my estimateValuable records
What usually qualifies
You choose which of these to include. It is always fine to leave any out.
- Commit and CI historyWhich changes broke the build and how they got fixed.
- Bugs and issue threadsHow problems get reproduced, prioritized and closed.
- Architecture notesThe reasons behind how your systems are built.
- Pull requests and reviewsWhat reviewers spot, what they challenge, and the reasons.
What teams ask most: code we do not own
Much of what agencies and consultancies build is owned by their clients. Ownership is worked through in scoping, and any client project can stay out. Whether a client needs to agree is for you and your counsel.
Tickets and logs mention customers. The de-identified copy swaps customer and developer names for placeholders.
Making the copy
Everything starts under an NDA. You are never asked for keys, tokens or passwords. Before anything is sent you approve a sample, and you can withhold any repo or product you consider core.
Short answers
What owners usually ask
Must our main product be included?
No. You can exclude any repo.
Do we pay anything for this?
No. There is no cost to you, and asking for an estimate does not commit you to anything.
Will just an issue tracker do?
It can be. A long, well-kept tracker is a good start.