hmm, easy enough to add an option to the method, but that alone would require usage to be hard coded. I wonder how we might want to control this option in general. Would it make sense to manage this via allowed_scm policy?

iirc correctly there are at least some instances where builds look at git history. I'm not a fan of that, but a case worth considering here.

Granted, I guess some of this could be follow up if all osbs needs is to hard code it.