Why is this needed?
Many matrixed workflows conditionally generate artifacts (i.e. Cypress videos or snapshots). The previous pattern in v3 was to simply upload artifact and set if-no-files-found: ignore. If there's artifacts, great...if not, no problem.
Given that the solution to accomplish the same task in v4 is to use the merge action. There should be a matching param so that in the event all the matrixed tests pass without issue, the merge job doesn't fail.
Solution
This loosely mirrors the functionality from the root action:
It uses an input of the same name for consistency
IMPORTANT: It uses error as the default (instead of warn as in the root action) to prevent breaking changes...however, I would love to change the default to warn for consistency...input welcome
It factors out a reused constant...in theory some input/error parsing could be shared too, but it might be just distinct enough to not matter
Fixes #520.
Why is this needed? Many matrixed workflows conditionally generate artifacts (i.e. Cypress videos or snapshots). The previous pattern in v3 was to simply upload artifact and set if-no-files-found: ignore. If there's artifacts, great...if not, no problem.
Given that the solution to accomplish the same task in v4 is to use the merge action. There should be a matching param so that in the event all the matrixed tests pass without issue, the merge job doesn't fail.
Solution This loosely mirrors the functionality from the root action: