Replies: 2 comments
-
I actually would suggest that we remove the start from template totally and swap it by --start-from-template=<github_repo>/name_of_template. The default should be start from blank unless the user explicitly specifies a template. The default workflow for the user is either they clone the repo, and then test agenta in one of the folders in example. Or they follow a tutorial based on a github repo. For organizations, I agree, but I think we should not show the user the option to select an organization if there is only one. |
Beta Was this translation helpful? Give feedback.
-
let's start with what we have and move adjusting --start-from-template=github repo to another issue |
Beta Was this translation helpful? Give feedback.
-
We aim to enhance the
agenta init
command to support a non-interactive mode, which would allow automation and integration into various workflows without the need for user intervention. This would be particularly useful in CI/CD pipelines and scripting use cases.Currently, the interactive setup requires user input, restricting our ability to fully automate the initialization process.
At present, executing
agenta init
does not provide a way to specify the organization or how to initialize the app (either as a "Blank App" or "Start from template").We plan to add two click options and their associated logic to the
agenta init
command:Beta Was this translation helpful? Give feedback.
All reactions