I started using this as nice extra check in my test workflows - which are then called as part of my release workflows.

In those scenarios I often do not need to see the summary table from this action - at least not when the action did not find anything relevent to report.

So my wish is a boolean input argument to hide the summary table - at least then the action does not fail or finds no issues.

Examples

Example 1: ghcr-manager/ghcr-manager Release 0.9.8

The release workflow triggers many tests, which themselves print summaries.

The summary from ensure-immutable-actions comes first, is quite large and with the header being so prominent makes this look a bit like a run for ensure-immutable-actions and less for that repo.

And as ensure-immutable-actions found nothing to complain plus is set to fail-on-mutable, I could well do without it's summary if it finds no issues.

FYI: This repo is a composite node action which is built when using it because it uses better-sqlite and afaik thus can't be precompiled.

Example 2: ghcr-manager/ghcr-untag-action Release 1.0.0

Here my visual issues are mainly being greeted with "Failed" in bold at the top of my release workflow - which does not fail.

The details below show it's actually an "unsupported" node24 action in the chain - the repos main action.yml itself called in test workflows.

And the ensure-immutable-actions here runs with fail-on-mutable too and does not fail - which to me makes the "Failure" title to the entire summary a bit misleading.

Note on that "unsupported" node24 action in example 2

At first I thought that this was incorrect or that I could filter it out with exclude-workflows: "./" or similar exclude patterns (none worked).

Turns out that this is absolutely correct by ensure-immutable-actions to flag this as this is a case of a node24 action (not composite) being run in an unusual way (live built and directly run during tests). And the proper solution is to exclude the test workflow which has uses: "./".

See here for the follow up release workflow in the same action repo (test workflow excluded, does not show in excluded-counts but I don't care).

And when ensure-immutable-actions scans the same action (ghcr-manager/ghcr-untag-action) being used in a normal way (pre-compiled running from a git-commit with a git-tag and github-release from it) then it reports it as Immutable and instead of "Failure" in the summary header it prints "All Passed". See here.