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

mepo init #282

Open
pchakraborty opened this issue May 1, 2024 · 0 comments
Open

mepo init #282

pchakraborty opened this issue May 1, 2024 · 0 comments
Assignees

Comments

@pchakraborty
Copy link
Collaborator

pchakraborty commented May 1, 2024

The init command is somewhat odd. In the current implementation, all it does is read components.yaml and create the state (.mepo/state.pkl). In the original design, it was meant to be followed by mepo clone. Since clone now has init folded in (i.e. has the ability to initialize the state), the standard way of using mepo is to start with the clone command

mepo clone -b <version> <url> <directory>

So it is possible to use init for some other purpose. For example, it can traverse a directory tree that has been manually prepared, find .git directories and create the registry (components.yaml), thereby initializing a mepo repository.

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

1 participant