Skip to content

feat: expose fail-on severity threshold in GitHub Action#82

Merged
Tim-Pohlmann merged 1 commit into
mainfrom
feat/action-fail-on
Jul 3, 2026
Merged

feat: expose fail-on severity threshold in GitHub Action#82
Tim-Pohlmann merged 1 commit into
mainfrom
feat/action-fail-on

Conversation

@Tim-Pohlmann

Copy link
Copy Markdown
Owner

Summary

  • Adds a fail-on input to action.yml (error/warning/info, default error) mirroring the CLI's --fail-on flag added in feat: add --fail-on option to control failing severity #77
  • Passes it through to the dolphin check invocation so composite-action users can control which severity level fails the workflow

Test plan

  • CI passes
  • Manually run the action with fail-on: warning in a downstream workflow and confirm it fails on warning-level findings

🤖 Generated with Claude Code

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>
@sonarqubecloud

sonarqubecloud Bot commented Jul 3, 2026

Copy link
Copy Markdown

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a configurable severity threshold to the Dolphin GitHub Action so users can choose which finding level (error/warning/info) should fail a workflow, matching the dolphin check --fail-on CLI behavior introduced in #77.

Changes:

  • Adds a new fail-on input to action.yml with default error.
  • Passes the selected threshold through to the action’s dolphin check invocation via --fail-on.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Tim-Pohlmann Tim-Pohlmann merged commit 1f1a9bb into main Jul 3, 2026
8 checks passed
@Tim-Pohlmann Tim-Pohlmann deleted the feat/action-fail-on branch July 3, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants