commits left behind on ot10

[jar398]

(initially reported Oct 30)

It would be nice to understand the following. It's fairly harmless given that it's on the development system, but assurance that something similar won't happen on the production system would be nice.

Using branch master of repo phylesystem-0
From https://github.com/OpenTreeOfLife/phylesystem-0
adb156f..22ed62e master -> origin/master
Branch master set up to track remote branch master from origin.
Warning: you are leaving 201 commits behind, not connected to
any of your branches:

adb156f Update Study #10 via OpenTree API
d452da9 Update Study #10 via OpenTree API
22e2792 Update Study #tt_18 via OpenTree API
b9d8986 Delete Study #tt_17 via OpenTree API
... and 197 more.

If you want to keep them by creating a new branch, this may be a good time
to do so with:

git branch new_branch_name adb156f

[mtholder]

I think these are caused by running my tests (phylesystem-api/ws-tests/run_tests.sh) on the dev server - they exercise some non-standard aspects of API. It would be nice to confirm that though...