Closed StanczakDominik closed 4 years ago
We ran into the issue of Azure not pulling git-lfs files during https://github.com/PlasmaPy/PlasmaPy-NEI/pull/21
As it turns out, adding lfs: true to the checkout step as in this change:
lfs: true
checkout
https://github.com/PlasmaPy/PlasmaPy-NEI/pull/21/commits/d3360c3cba0fe95e949ec7d0cc35495c7929e8c1
allows Azure to easily grab them.
This change was guided by Azure docs over at https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/pipeline-options-for-git?view=azure-devops#checkout-files-from-lfs
I didn't see any easy way of overriding this setting downstream, and I currently see no disadvantages to putting it in upstream.
I assume this doesn't cause any issues for repos not using lfs?
I expect so - I wouldn't see it breaking anything if LFS isn't used.
let's find out :grinning:
We ran into the issue of Azure not pulling git-lfs files during https://github.com/PlasmaPy/PlasmaPy-NEI/pull/21
As it turns out, adding
lfs: true
to thecheckout
step as in this change:https://github.com/PlasmaPy/PlasmaPy-NEI/pull/21/commits/d3360c3cba0fe95e949ec7d0cc35495c7929e8c1
allows Azure to easily grab them.
This change was guided by Azure docs over at https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/pipeline-options-for-git?view=azure-devops#checkout-files-from-lfs
I didn't see any easy way of overriding this setting downstream, and I currently see no disadvantages to putting it in upstream.