Only fetch lfs files for specific git_ref

[Tobias-Fischer]

Description

Currently conda-build fetches all lfs files that ever existed in the history. This is not necessary, and as outlined in #4809 is costly when e.g. using GitHub. For the specific use case that I have in mind (see RoboStack/ros-humble#155), the lfs files were actually removed from the repository and moved elsewhere (as the GitHub limits were exceeded, and now require payment), but the conda build still fails.

We already have the git_ref that we are interested in, so this is a relatively minor change; much smaller than making git-lfs completely optional as suggested in #4809

Checklist - did you ...

• Add a file to the news directory (using the template) for the next release's release notes?
• Add / update necessary tests?
• Add / update outdated documentation?

[conda-bot]

We require contributors to sign our Contributor License Agreement and we don't have one on file for @Tobias-Fischer.

In order for us to review and merge your code, please e-sign the Contributor License Agreement PDF. We then need to manually verify your signature, merge the PR (conda/infrastructure#881), and ping the bot to refresh the PR.

[kenodegard]

@conda-bot check

[Tobias-Fischer]

Hi @kenodegard - any chance to run this again, please?

[Tobias-Fischer]

I think this is ready to go - all CI failures are unrelated :)

[Tobias-Fischer]

A quick reminder @kenodegard :)

[kenodegard]

@Tobias-Fischer thanks for checking in, we're still working to resolve the unrelated test failures caused by upstream deprecations, once we untangle that we'll get this moving again

[codspeed-hq]

CodSpeed Performance Report

Merging #5202 will not alter performance

_{Comparing Tobias-Fischer:patch-1 (5a66529) with main (ab137d2)}

Summary

✅ 3 untouched benchmarks

[schuylermartin45]

I appreciate you providing the additional context in the PR notes. This looks pretty straight forward and a good win all-around. Thanks!