Answer:
The AtScale UI is a Git client and an AtScale Engine client. In order to maximize flexibility, the AtScale UI does not create a dependency between these two functions. Good Git practices should be exercised independent of good AtScale practices. As such, deploying a model can be done without a commit to Git.
We believe this has development value as a developer might not wish to commit to a repo without testing their changes ahead of time. Requiring a commit before deploy can lead to more unnecessary Git management. Once a developer believes the changes to the model meets the need, they can commit. Should a customer decide to institute a ‘commit before deploy’ practice, the AtScale platform does not prevent that practice.