[PATCH v3 12/13] ci: really use shallow clones on Azure Pipelines
- From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
- Date
- Oct 4, 2019, 15:09 UTC
- Message-ID
- <4495c392fd47db0b66c93b6d3d512ec606038471.1570201763.git.gitgitgadget@gmail.com>
- In-Reply-To
- <pull.288.v3.git.gitgitgadget@gmail.com>
From: Johannes Schindelin <johannes.schindelin@gmx.de>
This was a left-over from the previous YAML schema, and it no longer works. The problem was noticed while editing `azure-pipelines.yml` in VS Code with the very helpful "Azure Pipelines" extension (syntax highlighting and intellisense for `azure-pipelines.yml`...).
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> --- azure-pipelines.yml | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/azure-pipelines.yml b/azure-pipelines.yml index c329b7218b..55ee23ad0f 100644 --- a/azure-pipelines.yml +++ b/azure-pipelines.yml @@ -1,6 +1,5 @@ -resources: -- repo: self - fetchDepth: 1 +variables: + Agent.Source.Git.ShallowFetchDepth: 1 jobs: - job: windows_build
-- gitgitgadget