Editing .bitpocket/exclude results in unexpeced deletions & data loss about bitpocket HOT 4 CLOSED

See issue #20 for a probable cause.

from bitpocket.

I'm not familiar enough with bitpocket to completely understand that issue (#20), especially since I can't see a description of that, but perhaps that issue refers to the fact that an excluded file:

1: Ends up in .bitpocket/state/tree-current, but
2: Is not sent to the server on initial sync (because it's excluded), but
3: On syncing after changing exclude, it is observed as having once existed locally (because it's in tree-current), but not does not exist on master, and is therefore classified as having been deleted somewhere else.

That sounds convincing, and it also seems clear to me that the correct behavior would be that a file that is not sent to Master should also not be added to tree-current.

from bitpocket.

This is fixed in torfason/bitpocket@60dd63367e.
However, I'd recommend pulling the changes from torfason/bitpocket@bc67232bbf in that same repo instead of torfason/bitpocket@60dd63367e, since torfason/bitpocket@bc67232bbf has been much more extensively tested.

from bitpocket.

The fix described above was merged into sickill/bitpocket around a year ago, so this issue can be closed.

from bitpocket.