I think this PR will be a valuable addition to gh-migration-analyzer, as the diskUsage (named "Size") property can be a problem/blocker for migrations in the case of very large repositories.
Same with releases -- they count against a repository's metadata limit, so a repository with many release (assets) or enough large release assets will fail to migrate. A future addition to this would be to sum up the size of all release assets, as this will be a more direct indicator of migration problems.
I included the number of Discussions and number of Packages, because these properties are not migrated by GEI, so it would be nice to see at a glance which repositories will not fully migrate with GEI.
I included pushedAt and isArchived to identify repositories unsuitable for migrations. Archived repositories may not need to be migrated. And repositories that haven't seen a push in some time may be considered inactive, and may need not be migrated.
I think this PR will be a valuable addition to gh-migration-analyzer, as the
diskUsage
(named "Size") property can be a problem/blocker for migrations in the case of very large repositories.Same with releases -- they count against a repository's metadata limit, so a repository with many release (assets) or enough large release assets will fail to migrate. A future addition to this would be to sum up the size of all release assets, as this will be a more direct indicator of migration problems.
I included the number of Discussions and number of Packages, because these properties are not migrated by GEI, so it would be nice to see at a glance which repositories will not fully migrate with GEI.
I included
pushedAt
andisArchived
to identify repositories unsuitable for migrations. Archived repositories may not need to be migrated. And repositories that haven't seen a push in some time may be considered inactive, and may need not be migrated.