[m_ke]

How is it forcing code review on you?

I do agree that having things tied to a commit might not be ideal if you're running a lot of experiments in a large shared codebase.

I've been tempted to use git to version my model runs but always avoid it because it's usually just extra work.

[mlthoughts2018]

I think you flipped my comment around. I’m saying that the number one defining requirement of model reproducibility tooling is that it does force version control / code review.

It should force the concept of “running an experiment” to be just another instance of a deployment. Any part of running an experiment that happens outside of the scope of that, such as with “mlflow run ...” for example, is immediately violating the most basic property of the whole thing (I guess unless “mlflow run ...” is hacked to perform actual production deployments of all types of programs).