Azure-devops-docs: How to set ref to specific commit SHA?

[ggirard07]

According to multi-checkout design document, it should be possible to reference a specific commit ID to checkout. What is the proper syntax to achieve this while using the repository resource syntax?

Right now, if I simply put the full SHA (or even short SHA displayed in Github) as ref, I receive the following error message:

The pipeline is not valid. Could not get the latest source version for repository Me/MyRepo hosted on https://github.com/ using ref refs/heads/79c26b351f88e5b5842570d6c7d0447524b35a43. GitHub reported the error, "No commit found for SHA: refs/heads/79c26b351f88e5b5842570d6c7d0447524b35a43"

My repository resource looks like:

resources:
  repositories:
  - repository: MyGitHubRepo # The name used to reference this repository in the checkout step
    type: github
    endpoint: Me
    name: Me/MyRepo
    ref: 79c26b351f88e5b5842570d6c7d0447524b35a43

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 8a0499c0-bd1c-47a0-b472-54a5d6c159b4
• Version Independent ID: ec3feae0-4f23-68ab-6307-75fde645468a
• Content: Check out multiple repositories in your pipeline - Azure Pipelines
• Content Source: docs/pipelines/repos/multi-repo-checkout.md
• Product: devops
• Technology: devops-cicd
• GitHub Login: @steved0x
• Microsoft Alias: sdanie

[WilliamAntonRohm]

@ggirard07 -- thanks for your question. You may find answers here:

• Azure DevOps Support Bot

• Azure DevOps on Stack Overflow

  @steved0x -- please look into this issue.

[melezhik]

I also would like to get an answer to the same question.

[steved0x]

@ggirard07 @melezhik I'll find out and report back here shortly.

[melezhik]

Thumb 👍

On Feb 18, 2020 8:27 AM, "Steve Danielson" [e-mail] wrote:

@ggirard07 https://github.com/ggirard07 @melezhik
https://github.com/melezhik I'll find out and report back here shortly.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/vsts-docs/issues/7239?email_source=notifications&email_token=AAHRHSLJMSKVNOPL2GBFPVLRDPV3TA5CNFSM4KTHLKS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMCFF4Q#issuecomment-587485938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHRHSMQXMTXIYCO5AAIW6LRDPV3TANCNFSM4KTHLKSQ
.

[MatthiasMose]

@steved0x Do you have new information here?

[steffilion]

Same thing from here. I do experiment the same issue here

[anthraxn8b]

@steved0x Do you have new information for us? :-)

[cxwtool]

This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.

[ggirard07]

@cxwtool I really hope you are a bot and not a human... Do you think this issue looks like resolved when looking at the last messages?
No update in 180 days might be a good think to avoid all of the +1 replies and keep the thread clean!

[anthraxn8b]

This just means they are not able to handle the volume of Tickets.
The reason is either that they have to many bugs or to few support people...

[mijacobs]

@steved0x Can you take a look at this?