What happened?
I am not sure, but using archive: false, then it creates an artifact with the file name, ignoring name input.
When the same file name is used across multiple jobs in a workflow, the artifact name will be in conflict.
Then fails upload.
What did you expect to happen?
Should upload using the input name
How can we reproduce it?
Using this workflow.
jobs:
lint:
steps:
- uses: actions/checkout@v6
- uses: upload-artifact@v7
with:
name: report
archive: false
path: report.html
test:
steps:
- uses: actions/checkout@v6
- uses: upload-artifact@v7
with:
name: report
archive: false
path: report.html
Anything else we need to know?
No response
What version of the action are you using?
v7.0.0
What are your runner environments?
linux
Are you on GitHub Enterprise Server? If so, what version?
No response
What happened?
I am not sure, but using
archive: false, then it creates an artifact with the file name, ignoringnameinput.When the same file name is used across multiple jobs in a workflow, the artifact name will be in conflict.
Then fails upload.
What did you expect to happen?
Should upload using the input name
How can we reproduce it?
Using this workflow.
Anything else we need to know?
No response
What version of the action are you using?
v7.0.0
What are your runner environments?
linux
Are you on GitHub Enterprise Server? If so, what version?
No response