Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for libraries #35

Open
MkuuWaUjinga opened this issue Jul 22, 2023 · 1 comment
Open

Support for libraries #35

MkuuWaUjinga opened this issue Jul 22, 2023 · 1 comment

Comments

@MkuuWaUjinga
Copy link
Contributor

MkuuWaUjinga commented Jul 22, 2023

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)
@joshpxyne
Copy link
Owner

This is really great! Definitely worth taking a swing at!

Repository owner deleted a comment from Zakon1980 Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants