Currently, the plt switch and plt rm subcommands delete the previous local pallet without checking whether it has any changes which have not been uploaded to a remote Git repo. It would be better to only enable that behavior with a --force flag, and the default behavior should be changed so that plt switch/rm (without a --force flag) will only delete the previous local pallet when all of the following conditions are met:
the existing local pallet is a Git repo
all changes in the existing local pallet have been pushed to a remote Git repo
If either of those conditions are not met, it would be very nice if the plt switch/rm subcommand would provide a simple TUI (using https://github.com/charmbracelet/huh) to help the user back up their changes to GitHub before plt switch deletes the local pallet; we'd need a command-line flag (maybe a global --frontend=noninteractive) to disable interactivity, for use in scripts.
Currently, the
plt switchandplt rmsubcommands delete the previous local pallet without checking whether it has any changes which have not been uploaded to a remote Git repo. It would be better to only enable that behavior with a--forceflag, and the default behavior should be changed so thatplt switch/rm(without a--forceflag) will only delete the previous local pallet when all of the following conditions are met:If either of those conditions are not met, it would be very nice if the
plt switch/rmsubcommand would provide a simple TUI (using https://github.com/charmbracelet/huh) to help the user back up their changes to GitHub beforeplt switchdeletes the local pallet; we'd need a command-line flag (maybe a global--frontend=noninteractive) to disable interactivity, for use in scripts.