tracking bleeding edge changes with some rare platforms or modern
compilers on scheduled basis is not what usually forks do. let's
skip by default in forks, if some fork is interested, it might be
enabled locally
---
 .github/workflows/cross-zoo.yml      | 1 +
 .github/workflows/fedora-rawhide.yml | 1 +
 2 files changed, 2 insertions(+)

diff --git a/.github/workflows/cross-zoo.yml b/.github/workflows/cross-zoo.yml
index d9864e298..5abd9cbcd 100644
--- a/.github/workflows/cross-zoo.yml
+++ b/.github/workflows/cross-zoo.yml
@@ -90,6 +90,7 @@ jobs:
           }
         ]
     runs-on: ubuntu-latest
+    if: ${{ github.repository_owner == 'haproxy' }}
     steps:
     - name: install packages
       run: |
diff --git a/.github/workflows/fedora-rawhide.yml 
b/.github/workflows/fedora-rawhide.yml
index 8f2578154..1bb274557 100644
--- a/.github/workflows/fedora-rawhide.yml
+++ b/.github/workflows/fedora-rawhide.yml
@@ -14,6 +14,7 @@ jobs:
         cc: [ gcc, clang ]
     name: ${{ matrix.cc }}
     runs-on: ubuntu-latest
+    if: ${{ github.repository_owner == 'haproxy' }}
     container:
       image: fedora:rawhide
     steps:
-- 
2.43.2


Reply via email to