In some cases (plugins, OSBS) it could be worth to use --depth 1 when they are sure history is not used during the build.
--depth 1
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.
Metadata Update from @mikem: - Custom field Size adjusted to None
Metadata Update from @mikem: - Issue set to the milestone: 1.37 (was: 1.36)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/4130
Please continue any further discussion there.