Why did GitHub import miss part of my repo?
Maps · Updated Jun 22, 2026
Repo import creates an editable draft from detected files and dependencies. Some services may need to be added manually.
Repo import scans repository metadata and dependency files to create a first draft. It is designed to give you an editable map, not a locked or perfect diagram. The repo import docs explain what the scan reads.
Generated code, unusual monorepo layouts, private package metadata, and services that are not represented in dependency files may need manual cleanup. If the scan finds more nodes than your plan allows, the map stays within the current node limit.
After import, review the map, rename services, connect missing edges, add owners, and fill in spend metadata.
Related articles
How does repo import work?
MapsRepo import scans a connected GitHub repository and drafts a map from detected services, frameworks, and dependencies.
How do I create my first map?
MapsStart from a blank canvas, import a repo, paste canopy.json, or clone a template. Each path lands on the same editable map.
What happens when I delete a map?
MapsDeleting a map you own removes it and its nodes and edges. If the map has been sold, it is archived instead so buyers keep access.