Why?
Since this repo is designed to be used together with Azure/mlops-v2, files in this template that make use of relative paths need to coordinate with the way this repo is changed after sparse_checkout.sh is run.
How?
So that developers on this repo don't need to track the impacts of changes to a distinct repo (Azure/mlops-v2), it seems easier to develop and maintain relative paths in files in this repo if they are written relative to the folder structure of this repo as it is, rather than as it will be after a script from another repo, like sparse_checkout.sh, is run.
Anything else?
Why?
Since this repo is designed to be used together with Azure/mlops-v2, files in this template that make use of relative paths need to coordinate with the way this repo is changed after sparse_checkout.sh is run.
How?
So that developers on this repo don't need to track the impacts of changes to a distinct repo (Azure/mlops-v2), it seems easier to develop and maintain relative paths in files in this repo if they are written relative to the folder structure of this repo as it is, rather than as it will be after a script from another repo, like sparse_checkout.sh, is run.
Anything else?