Added note to explain about fetchDepth restriction

[seanarmstrong87]

Added a note in the giversion execute docs to explain that fetchDepth 0 is required

[brendonofficial]

You have required to use fetchDepth of 0 in your comment, but fetchDepth: 1 in your example.

There is an existing note in the Github usage example, perhaps it can be copied from there?

[arturcic]

I agree with that, we need to add the note as well, would be nice to keep them in sync as they share the same interface but different implementations.

[seanarmstrong87]

Sorry I was rushing and am now on holiday for 2 weeks so it will have to wait unless you want to do it?

…

On Sat, 17 Sep 2022 at 14:58, Artur ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In docs/examples/azure/gitversion/execute/usage-examples.md <#736 (comment)>: > @@ -4,6 +4,13 @@ Find out how to use the **gitversion/execute** task using the examples below. > The examples use the latest _0.x_ version of the GitVersion Execute task. It is recommended to use the latest released version in your own pipelines. +Note that if the pipeline is setup to use a shallow git fetch mode the GitVersion Execute task will fail. It is required to use fetchDepth of 0 like so: + +```yaml +- checkout: self + fetchDepth: 1 I agree with that, we need to add the note as well, would be nice to keep them in sync as they share the same *interface* but different implementations. — Reply to this email directly, view it on GitHub <#736 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE4TJNBRHQSZSZY6MDXIKITV6W55ZANCNFSM6AAAAAAQOA7XQI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[arturcic]

@seanarmstrong87 any updates on this one?

[seanarmstrong87]

@arturcic Updated

[mergify]

Thank you @seanarmstrong87 for your contribution!