You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@superset.apache.org by ma...@apache.org on 2024/04/11 00:44:45 UTC
(superset) 01/01: chore: remove no-op.yml as it's not needed anymore
This is an automated email from the ASF dual-hosted git repository.
maximebeauchemin pushed a commit to branch no-no-op-op
in repository https://gitbox.apache.org/repos/asf/superset.git
commit e0c41569da1b5675e7452a564eebada75780083e
Author: Maxime Beauchemin <ma...@gmail.com>
AuthorDate: Wed Apr 10 17:44:26 2024 -0700
chore: remove no-op.yml as it's not needed anymore
---
.github/workflows/no-op.yml | 96 ---------------------------------------------
1 file changed, 96 deletions(-)
diff --git a/.github/workflows/no-op.yml b/.github/workflows/no-op.yml
deleted file mode 100644
index e56177239b..0000000000
--- a/.github/workflows/no-op.yml
+++ /dev/null
@@ -1,96 +0,0 @@
-# no-op.yml
-#
-# Purpose:
-# This workflow provides a workaround for the "required status checks" feature in GitHub Actions
-# when using path-specific conditions in other workflows. Required checks might remain in a "Pending"
-# state if the conditions are not met, thus blocking pull requests from being merged.
-# This no-op (no operation) workflow provides dummy success statuses for these required jobs when
-# the real jobs do not run due to path-specific conditions.
-#
-# How it works:
-# - It defines jobs with the same names as the required jobs in the main workflows.
-# - These jobs simply execute a command (`exit 0`) to succeed immediately.
-# - When a pull request is created or updated, both this no-op workflow and the main workflows are triggered.
-# - If the main workflows' jobs don't run (due to path conditions), these no-op jobs provide successful statuses.
-# - If the main workflows' jobs do run and fail, their failure statuses take precedence,
-# ensuring that pull requests are not merged with failing checks.
-#
-# Usage:
-# - Ensure that the job names in this workflow match exactly the names of the corresponding jobs in the main workflows.
-# - This workflow should be kept as-is, without path-specific conditions.
-
-name: no-op Checks
-on: pull_request
-
-jobs:
- frontend-build:
- runs-on: ubuntu-latest
- steps:
- - name: No-op for frontend-build
- run: exit 0
-
- pre-commit:
- strategy:
- matrix:
- python-version: ["3.10"]
- runs-on: ubuntu-latest
- steps:
- - name: No-op for pre-commit
- run: exit 0
-
- python-lint:
- strategy:
- matrix:
- python-version: ["3.10"]
- runs-on: ubuntu-latest
- steps:
- - name: No-op for python-lint
- run: exit 0
- test-postgres-hive:
- strategy:
- matrix:
- python-version: ["3.10"]
- runs-on: ubuntu-latest
- steps:
- - name: No-op for frontend-build
- run: exit 0
- test-postgres-presto:
- strategy:
- matrix:
- python-version: ["3.10"]
- runs-on: ubuntu-latest
- steps:
- - name: No-op for frontend-build
- run: exit 0
- unit-tests:
- strategy:
- matrix:
- python-version: ["3.10"]
- runs-on: ubuntu-latest
- steps:
- - name: No-op for frontend-build
- run: exit 0
- test-mysql:
- strategy:
- matrix:
- python-version: ["3.10"]
- runs-on: ubuntu-latest
- steps:
- - name: No-op for test-mysql
- run: exit 0
- test-postgres:
- strategy:
- matrix:
- python-version: ["3.10", "3.11"]
- runs-on: ubuntu-latest
- steps:
- - name: No-op for test-postgres
- run: exit 0
- test-sqlite:
- strategy:
- matrix:
- python-version: ["3.10"]
- runs-on: ubuntu-latest
- steps:
- - name: No-op for test-sqlite
- run: exit 0