bandicot

Versions sees commits made outside Bandicot

A commit you make in a terminal or another app now shows up in Versions as its own version, and nothing you have not committed is lost.

Product

In a project that uses git, a commit made outside Bandicot, in a terminal or another app, now appears in Versions as its own version, named by the commit message. The History page lists it beside the versions Bandicot saved, in the order things happened.

The files you have not committed yet are saved first, so importing a commit never replaces work in progress. While git is in the middle of a rebase, a merge or a cherry-pick, Versions waits and imports the result when it ends.

Bandicot looks at git only when something changed, and a quiet project costs a few file checks. A repository it cannot read is left alone and never stops a save.