-
Notifications
You must be signed in to change notification settings - Fork 26
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
🚀 Feature: Support Initializing a Project in an Existing Organization #83
Comments
@stnguyen90 Please assign this issue token to me? |
Hi, we have already assigned you two issues. That’s the maximum number of issues we can assign at a time to one person |
I'd like to get assigned! |
Hi @probablyArth, I've assigned the issue to you! Happy Hacktoberfest 🎃! Notes: Please update us with your progress every 3 days, so that we know you are working on it. |
Here's what I have in mind :-
|
@gewenyu99 what do you think of this? Perhaps the first "How would you like to start?" should have two options:
"Use an existing organization" would show a list of organizations (teams) the user can select from. Make sure to show the organization name and ID like we do for project. Then, ask, "Would you like to create a new project or link to an existing?". If they select "Link this directory to an existing Appwrite project" make sure to filter the results to the projects under the chosen organization. This would help when you have the same project name in multiple organizations. |
I like this approach. Make sure to include a non-interactive option! |
got it, ill start working on it 👌 |
Hi, are you working on it? If not, we will be reassigning the issue to the next person due to inactivity from your end. |
🔖 Feature description
Right now, initializing a project creates a new organization:
sdk-for-cli/lib/commands/init.js
Lines 32 to 37 in b461997
It would be helpful to allow creating as part of an existing organization.
🎤 Pitch
Creating in an existing organization makes organizing the project easier/cleaner.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: