Use sparse checkout instead of remote tracking#25847
Conversation
|
|
||
| # git fetch on fork repo | ||
| Write-Host "git fetch $remoteName $(DailyDocsBranchName)" | ||
| git fetch $remoteName "$(DailyDocsBranchName)" |
There was a problem hiding this comment.
@benbp it would be good to understand why adding another remote and then fetching a branch to checkout doesn't work as expected when using sparse checkout. https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1233498&view=logs&j=dc056dfc-c0cf-5958-c8c4-8da4f91a3739&t=d08ed1f2-0ec2-5498-48a9-682643d126ca
There was a problem hiding this comment.
Based on git man documentation, git fetch do downloading the deltas besides of sparse checkout files.
There is no sparse checkout like functionality for git fetch
https://git-scm.com/docs/git-remote#Documentation/git-remote.txt-emaddem
There was a problem hiding this comment.
There was a problem hiding this comment.
I don't think that is the same situation that we have here. We already do the no-checkout on clone but we should be able to add a remote and then fetch a new set of commits down and checkout just those changes.
Rename Microsoft.StorageTasks to Microsoft.StorageActions (Azure#25847) * Replace Microsoft.StorageTasks to Microsoft.StorageActions * Updating readme.md file and OperationsList Example
3 participants
Description
git remote + git fetch together is doing clone job which downloads all delta changes besides of
/metadata/,package.json.Using sparse checkout is less expensive for docs repo.
Testing pipeline: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1233606&view=logs&j=5e8cddd4-765d-5046-f31f-2d7d6b215293&t=f589ca01-2aac-4ede-b74c-f8d152bfdd02
Error one: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1233498&view=logs&j=dc056dfc-c0cf-5958-c8c4-8da4f91a3739&t=d08ed1f2-0ec2-5498-48a9-682643d126ca
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines