Sparse checkout should handle private repos

[danieljurek]

No description provided.

[benbp]

@danieljurek I couldn't get the PAT formatting syntax right at the time based on what devops gave the task, but I believe there are some promising examples here: https://github.com/MicrosoftDocs/azure-devops-docs/issues/2455

[danieljurek]

Have we considered ~/.git-credential?

          git config --global user.name "azure-sdk"
          git config --global user.email "[email protected]"
          echo "https://azure-sdk:$(example-pat-secret)@github.com" > ~/.git-credentials
          git config --global credential.helper "store"

I haven't needed to use a PAT on a per-repo basis. At this point one PAT has sufficed but I'd be glad to investigate if we'll need that.

@benbp

[weshaggard]

There is also persistCredentials option for an explicit checkout https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/steps-checkout?view=azure-pipelines that we might be able to use to get the correct credentials setup.

[benbp]

@weshaggard possibly if we can also set checkout: none but it might get tricky regarding whether you can define that field multiple times or if it would conflict with usage of pipelines where it should not be set to none (e.g. when defining multiple checkouts).

[JimSuplizio]

@danieljurek, @benbp and I chatted and we're closing this one out. It's been almost 2 1/2 years, and this clearly isn't going to get fixed.

[weshaggard]

I'm fine closing this but we may need to solve this for other reasons in the future.