-
Notifications
You must be signed in to change notification settings - Fork 2
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
ability to rename project #8
Comments
Please assign this issue to me |
All yours maddy. Thanks for pitching in! :D Please note that |
Just to be explicit. I don't think there needs to be a check if the "new name" already exists, but 🤔 I wonder if there should be a check with the user. Something like "Hey, [new name] already exists. Do you want to merge [old name]'s records into it?" |
Damn. just realized that if the target name exists then you have to repoint all the I was planning on "merge projects" as a separate ticket, but i think they're ultimately the same thing @maddy020. Sorry that the complexity of this one is growing. If you just want to do a tiny PR that only renames IF the target name isn't already used I'd be fine with that. I can handle the merge stuff separately. |
You still planning on poking this @maddy020 ? |
Ohh @masukomi |
Should the fix for this issue also add a edit: Or maybe the command would be |
Sorry been heads down in job-hunt land and accidentally removed "check github notifications" from the main part of my daily checklist... and thus kept forgetting to check 🤦♀️ i like (now to tackle the open PRs... ;) ) |
@maddy020 if you're still interested it'd prolly just be a change to the |
proposed interface
hey rename project <old name> <new name>
Behind the scenes this would just need to do a
Project names should be unique, and can't be "archived", so this change should be safe without other constraints.
The text was updated successfully, but these errors were encountered: