summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEdward Thomson <ethomson@edwardthomson.com>2019-12-03 18:09:03 +1100
committerEdward Thomson <ethomson@edwardthomson.com>2019-12-03 18:09:03 +1100
commit9c30fbed485d901b996d858b8a3dfa4a7a1ec91b (patch)
treeec79df91c253762db177c315b7a920cf69b52fd4
parent36bfc27a45ac34e8425271c9d3c79ce62564e195 (diff)
downloadlibgit2-9c30fbed485d901b996d858b8a3dfa4a7a1ec91b.tar.gz
ci: only push docs from the libgit2/libgit2 repoethomson/publish_docs_on_master
Users may fork libgit2 and run libgit2's CI on that, which is delightful! However, if they do, we'll fail the documentation publish phase, which is correct (because we don't allow them to publish _their_ version of the docs) but regrettable (since it should not fail). Only run the documentation publish phase when we merge branches into the libgit2/libgit2 repo.
-rw-r--r--azure-pipelines.yml2
1 files changed, 1 insertions, 1 deletions
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
index 75e4ef7c3..5ee741ce0 100644
--- a/azure-pipelines.yml
+++ b/azure-pipelines.yml
@@ -174,4 +174,4 @@ jobs:
echo 'password $(GITHUB_PAT)' >> ~/.netrc
git push origin gh-pages
displayName: 'Publish Documentation'
- condition: eq(variables['Build.Reason'], 'IndividualCI')
+ condition: and(eq(variables['Build.Repository.Name'], 'libgit2/libgit2'), eq(variables['Build.Reason'], 'IndividualCI'))