You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Killing projects is dangerous for anyone using this for billing purposes.
As such i think that there should be a -f / --force option for this. If the flag isn't passed then the project is actually just archived. This is a personal time tracker so the amount of data we're talking about is negligible and not going to cause anyone problems
this, of course, means we need a way to see a list of "archived" projects...
I'm thinking maybe a hey archives command which would, initially, just list archived projects, but if we decide to archive people instead of deleting it could have a section for them too.
and then a way to unarchive a project:
hey unkill project <name> ? 🤔 I'm unsure about unkill vs unarchive
I don't want to do a hey kill project <x> AND hey archive project <x> because it's too easy to move fast and accidentally do the dangerous one. really deleting should require the extra thought / effort of adding --force
The text was updated successfully, but these errors were encountered:
originated in this comment by @codesections
Killing projects is dangerous for anyone using this for billing purposes.
As such i think that there should be a
-f
/--force
option for this. If the flag isn't passed then the project is actually just archived. This is a personal time tracker so the amount of data we're talking about is negligible and not going to cause anyone problemsthis, of course, means we need a way to see a list of "archived" projects...
I'm thinking maybe a
hey archives
command which would, initially, just list archived projects, but if we decide to archive people instead of deleting it could have a section for them too.and then a way to unarchive a project:
hey unkill project <name>
? 🤔 I'm unsure aboutunkill
vsunarchive
I don't want to do a
hey kill project <x>
ANDhey archive project <x>
because it's too easy to move fast and accidentally do the dangerous one. really deleting should require the extra thought / effort of adding--force
The text was updated successfully, but these errors were encountered: