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

what should we put in .mp/ #6

Open
naturallymitchell opened this issue Dec 11, 2018 · 4 comments
Open

what should we put in .mp/ #6

naturallymitchell opened this issue Dec 11, 2018 · 4 comments

Comments

@naturallymitchell
Copy link
Member

definitely full import so we can pluck from it
but what about a full copy of whatever else is imported
then we can do reset or something to get back to what the import wants

@sh-zam
Copy link
Collaborator

sh-zam commented Dec 11, 2018

I'm trying to figure this out by looking at peru's code. Simple copy-paste from .mp doesn't seem much reliable.

@naturallymitchell
Copy link
Member Author

what wouldn't be reliable about it?
could we do a sanity check of src and dest before doing it?

peru does something different. it doesn't expect you to make any persistent edits to the import destinations, unless you use "overrides"

@sh-zam
Copy link
Collaborator

sh-zam commented Dec 12, 2018

Changing something in .mp/
Verifying .mp/ with the remote branch should resolve the reliability issue.

@naturallymitchell
Copy link
Member Author

after changing plucked files, mp should make it easy to copy them back into .mp/ so they can be pushed

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