Repository navigation
Replies: 1 comment
|
Currently, "omk init" is mostly intended for new or empty projects. It does not yet fully scan an existing arbitrary repo, restructure it into OMK’s layout, and generate all documentation automatically. For existing projects, the safer workflow is to run "omk init" in a separate branch/temp directory, compare the generated structure, and migrate/adapt the project incrementally. This is planned to be improved in "v1.1.18" with an "adopt" / "import"-style flow that can scan an existing project, infer its structure, generate README/context docs, and propose or apply a migration plan. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The init command creates the basic structure for an empty project. Is there any way to have it scan an already existing project with a different structure, fundamentally restructure it to the one used by omk, and fill in the necessary documentation (readme.md etc.) based on the project? Or what would be the way to use omk on these different projects?
I am omk noob yet, sorry if this is basic stuff.
All reactions