You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by ka...@apache.org on 2021/09/12 02:15:49 UTC
[airflow] 01/01: Fix broken link in ``dev/REFRESHING_CI_CACHE.md``
This is an automated email from the ASF dual-hosted git repository.
kaxilnaik pushed a commit to branch fix-nroken-link
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 3eb9155327161b38c6ce20e8311b5b92af0438d6
Author: Kaxil Naik <ka...@gmail.com>
AuthorDate: Sun Sep 12 03:12:40 2021 +0100
Fix broken link in ``dev/REFRESHING_CI_CACHE.md``
The link was broken
---
dev/REFRESHING_CI_CACHE.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev/REFRESHING_CI_CACHE.md b/dev/REFRESHING_CI_CACHE.md
index c5a27ee..19cdaa1 100644
--- a/dev/REFRESHING_CI_CACHE.md
+++ b/dev/REFRESHING_CI_CACHE.md
@@ -34,7 +34,7 @@ merges to `main` branch have separate maintenance step that take care about refr
used to speed up our builds and to speed up rebuilding of [Breeze](../BREEZE.rst) images for development
purpose. This is all happening automatically, usually:
-* The latest [constraints](../COMMITTERS.rst#pinned-constraint-files) are pushed to appropriate branch
+* The latest [constraints](../CONTRIBUTING.rst#pinned-constraint-files) are pushed to appropriate branch
after all tests succeeded in `main` merge or in `scheduled` build
* The [images](../IMAGES.rst) in `ghcr.io` registry are refreshed after every successful merge to `main`