]> git.ipfire.org Git - thirdparty/git.git/commit - azure-pipelines.yml
projects / thirdparty / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ab7d854) | patch
ci: really use shallow clones on Azure Pipelines
authorJohannes Schindelin <johannes.schindelin@gmx.de>
Fri, 4 Oct 2019 15:09:35 +0000 (08:09 -0700)
committerJunio C Hamano <gitster@pobox.com>
Sun, 6 Oct 2019 00:07:44 +0000 (09:07 +0900)
commitb35304bf958812a99dcbda366670ddc7bf9e086d
treea2657104f64b84b7298e4f7e5ce6947007006f32tree | snapshot
parentab7d854abaada90febf5b2e0839dd662cb0c8d10commit | diff
ci: really use shallow clones on Azure Pipelines

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>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
azure-pipelines.yml diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.