homesick deleted entire directory - sort of

[brettswift]

I've been using homesick for a few years. I don't commit to my castle often which is probably my problem. I am very proficient with git, and think homesick works the same way but I find it gets in my way more than helps because of some unique things about it.

As I'm pretty comfortable with git I'll probably ditch homesick for just a bare git repo and a global alias. I don't use many of the other features of homesick like multiple castles etc.

Thought I'd share some feedback - as I did enjoy homesick for a while.

(some omitted)

 9971  homesick status
 9972  homesick add -u
 9973  homesick diff --staged -- home/.aws/config
 9974  homesick diff dotfiles  --staged -- home/.aws/config
 9975  homesick diff dotfiles
 9979  ./.config
 9980  ./nvim
 9982  homesick add *
 9983  homesick track *
 9986  homesick track .
 9987  homesick status

That is what my brain did on a Monday morning. It tripped me up though. I wanted to add the entire ~/.config/nvim directory but just running homesick add . or track rather, the pathing was weird. (/home/.config I think?)

Anyways, the end result was that homesick track * added the nvim directory at the root of my castle. For a while I thought it deleted all my files until I did a homesick cd and went looking for them.
I was able to recover them, but in my opinion any add should work whether I'm relative or not, as git does.

It's also confusing to have the track command .. and all the --staged commands I couldn't send to git. I think the way to do it would be to go into the castle directory and run those commands with git natively.

Maybe I'm doing it wrong.. or not using homesick correctly. But if it helps to hear one guys experience then great! Thanks for all the fish!