Łukasz Mitka

Pretty much what I have described above. I have multiple repos with multiple workflow files with multiple actions. Some of the Actions I want to trust e.g. `actions/*`, my orgs...

@StevenMaude @norman-zon I've created a separate ticket #945 since this one tries to address different issue and doesn't sound doable with current Actions architecture. @staabm For parallel steps see this...

@smac89 It still would be a good feature for actions following semver.

@arximboldi you can try clearing GH cache (where ccache data is stored) https://stackoverflow.com/questions/63521430/clear-cache-in-github-actions

I've seen it, still the issue is opened and can help someone :)

@styfle This is valuable PR since it simplifies action usage. Please consider merging it.

I would go with not event trying to install library charts. Since it's not possible just skip them. For anyone looking for a workaround: Create separate config file for install...

Actually `commit:` version could be vastly improved by using `listWorkflowRuns` with `head_sha` parameter. https://github.com/dawidd6/action-download-artifact/issues/226

@sidx1024 https://github.com/dawidd6/action-download-artifact/pull/227 has been merged and released. `commit` should no longer trigger so many API calls. Just an FYI since documentation could still be useful for other options.

bad bot. Still needed.