From 853d5f0d609703ba86e55aeff3814d504c9cb4c4 Mon Sep 17 00:00:00 2001
From: Tim Pohlmann <tim@pohlmann.team>
Date: Fri, 3 Jul 2026 21:51:17 +0000
Subject: [PATCH] feat: expose fail-on severity threshold in GitHub Action

The --fail-on CLI flag (added in #77) was never wired into action.yml,
so composite-action users had no way to control which severity level
fails the workflow.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 action.yml | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/action.yml b/action.yml
index be550db..b951fa7 100644
--- a/action.yml
+++ b/action.yml
@@ -11,6 +11,10 @@ inputs:
     description: Directory to scan (defaults to the repository root)
     required: false
     default: ''
+  fail-on:
+    description: Lowest severity that causes a non-zero exit: error, warning, or info
+    required: false
+    default: error
 runs:
   using: composite
   steps:
@@ -35,5 +39,6 @@ runs:
       env:
         ACTION_PATH: ${{ github.action_path }}
         DOLPHIN_CWD: ${{ inputs.working-directory }}
+        DOLPHIN_FAIL_ON: ${{ inputs.fail-on }}
       run: |
-        node "$ACTION_PATH/launcher/launcher.js" check --cwd "${DOLPHIN_CWD:-$GITHUB_WORKSPACE}" --format github
+        node "$ACTION_PATH/launcher/launcher.js" check --cwd "${DOLPHIN_CWD:-$GITHUB_WORKSPACE}" --format github --fail-on "${DOLPHIN_FAIL_ON:-error}"