Download from a different workflow

[owenfarrell]

Describe the enhancement

Add support for downloading artifacts from other workflows and/or previous workflow runs.

Code Snippet

Adding an optional parameter that defines search criteria would provide the ability to reference other workflows and previous executions as necessary. For example:

// Representative new behavior
const previousWorkflowRunCriteria : WorkflowCriteria = {
    branch: 'master',
    event: 'push',
    status: 'success'
}
const artifactsFromPreviousRunOfThisWorkflow = await artifactClient.downloadAllArtifacts(path, previousWorkflowRunCriteria)

const anotherWorkflowCriteria : WorkflowCriteria = {
    owner: 'owenfarrell',
    repo: 'vscode-vault',
    workflow: 'Build'
}
const artifactsFromAnotherWorkflow = await artifactClient.downloadAllArtifacts(path, anotherWorkflowCriteria)

// Existing behavior
const artifactsFromThisRunOfThisWorkflow = await artifactClient.downloadAllArtifacts(path)

Additional information

Per the report in actions/download-artifact#3, a common use case amongst GitHub Actions users is to download an artifact from a previous run (or from another workflow altogether). This request serves as a precursor to resolving the linked issue above.

[bradennapier]

https://github.com/bradennapier/eslint-plus-action/blob/master/src/artifacts.ts

Looks like this is more common of a request than I iamgined! Just letting y'all know I needed the same thing and ended up just using the API to do it - some of the fn's i built may be useful to you. I am using them to allow forked PR's to work securely and for retaining small bits of state across the repo.

Feel free to open issue on the repo if you have any questions - took forever to figure out how to get all that done!

[fkirc]

This seems to be a duplicate of actions/download-artifact#3; is there any timeline of when something like #517 might be merged?

[owenfarrell]

This seems to be a duplicate of actions/download-artifact#3

@fkirc - Based on the pattern that download-artifact has used to date, where the action provides a thin layer for environmental interaction and delegates all calls to toolkit, I don't think these are duplicate issues.

This issue essentially serves as a dependency or prerequisite - functionality that needs to be in place in order for download-artifact to implement the "last mile" of capabilities (containerization, environmental variables, etc.).