For the sake of convenience I've added MiniObserve as a subtree for now. At some point I want to publish it as a package, then we can delete it again.
As long as you don't make any changes within the MiniObserve directory you can safely ignore the fact that it is a subtree. If you do, the only important thing to keep in mind is not to mix commits that change MiniObserve with those that don't (and that's also mostly an issue of aesthetics).
For the sake of convenience I've added MiniObserve as a subtree for now. At some point I want to publish it as a package, then we can delete it again.
As long as you don't make any changes within the MiniObserve directory you can safely ignore the fact that it is a subtree. If you do, the only important thing to keep in mind is not to mix commits that change MiniObserve with those that don't (and that's also mostly an issue of aesthetics).