You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, gpt-migrate only works with code repositories that run as applications with a main file as entry point. However, many code bases are libraries. Libraries are different in that they:
Don't have a dedicated entry point
Often come with a test suite
The migration problem is equally important, so I think it'd be great if gpt-migrate could support this. For that, we'd have to allow for:
Several entry points (or no entry point and a separate logic to determine all sources of the dependency DAG)
The possibility to specify your own test suite (and migrate it to the new target repo if possible)
The text was updated successfully, but these errors were encountered:
Currently, gpt-migrate only works with code repositories that run as applications with a main file as entry point. However, many code bases are libraries. Libraries are different in that they:
The migration problem is equally important, so I think it'd be great if gpt-migrate could support this. For that, we'd have to allow for:
The text was updated successfully, but these errors were encountered: