This needs a bit more work as the artifacts are downloaded later and processed in report-to-issues.

@kevin940726 mind giving this another review and blessing when you have a chance?

Unfortunately, there's another breaking change I didn't see mentioned in the migration guide 😅. If we use the pattern field, the step outcome will still be success even though no data is downloaded. I guess we'll need an intermediate step to determine if any report is downloaded.

This can be a follow-up though. 👍

Unfortunately, there's another breaking change I didn't see mentioned in the migration guide 😅. If we use the pattern field, the step outcome will still be success even though no data is downloaded. I guess we'll need an intermediate step to determine if any report is downloaded.

I wonder if we can use the download-path output from the action to check that an artifact was downloaded successfully. The documentation around that output is a bit scarce though. My thinking is using that in an if statement to check for an empty value, which we can use to assume nothing was downloaded.

I don't think there's any harm in adding that into this PR. I can do some experimenting later this week.

Based on the code at: https://github.com/actions/download-artifact/blob/f44cd7b40bfd40b6aa1cc1b9b5b7bf03d3c67110/src/download-artifact.ts#L125

It will still set the output even though it downloads nothing 😆. I think the only option we have is to add a bash script to check the emptiness of the directory right after the download-artifacts step.

Superseded by #61338.