-
Notifications
You must be signed in to change notification settings - Fork 174
[feat] One command framework switch #265
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
Comments
This is super easy in theory, but what do we do about their existing code? Init in a new directory? Include git? I actually like the idea of tracking changes we make to their codebase so they can revert if something goes wrong. |
init in a new directory is my thought right now. we included git initially, but ran into a lot of issues. i'm very open to it, but we need to look up the directory tree and make sure that there isn't an existing git repo. there may have been other issues that led me to pull it out early on. I'm very down to add it and see what comes of it :) |
@bboynton97 brought up the brilliant idea of tracking a framework migration via branching. TODO |
bundle
into
eventually the switch command can also do other layers
The text was updated successfully, but these errors were encountered: