Industries / Software teams
How your team really builds and ships
Pull requests, review threads, tickets and architecture docs show how software gets built and maintained over years. That record is what labs look for. Client code and customer details can be excluded.
Check my estimateUseful records
Records that often qualify
Which of these go in is your call, and skipping any of them is always fine.
- Reviews and pull requestsThe catches, pushback and reasoning of your reviewers.
- Design docsWhy systems are built the way they are.
- Issues and bug reportsThe way issues get reproduced, prioritized and resolved.
- Commit and CI historyWhich changes broke the build and how each was fixed.
The concern we hear most: code we do not own
Agencies and consultancies often build code their clients own. Ownership is worked through in scoping, and any client project can stay out. You and your counsel decide whether a client needs to consent.
Customers show up in tickets and logs. Customer and developer names become placeholders in the de-identified copy.
How the copy is made
An NDA is in place from the start. You are never asked for keys, tokens or passwords. You approve a sample before anything goes out, and you can hold back any repo or product you consider core.
In brief
What owners usually ask
Will just an issue tracker do?
It may be. A long, well-kept tracker makes a good start.
Does any of this cost us?
No. It is free for you, and requesting an estimate commits you to nothing.
Do we need to include our main product?
No. Any repository can be left out.