Specify output filename
SharkFourSix opened this issue · comments
SharkFourSix commented
How do you specify the output name. I need to specify the name myself because I want to use the file in another file which in not part of the build steps.
sam commented
Unfortunately, this action doesn't support specifying the output file name. I made this action quite a while ago and there are a few things to improve, that's one of them. For now, you can add your own step where you run a shell command to rename the file, e.g:
jobs:
publish:
runs-on: ubuntu-latest
name: Publish Document
steps:
- name: Checkout
uses: actions/checkout@v2
- name: Publish PDF Document
uses: shrink/actions-document-publish@v1
id: publish-document
with:
sources: 'documents/front.md documents/examples/**/*.md documents/back.md'
- run: mv ${{ steps.publish-document.outputs.pdf }} your-file-name.pdf
SharkFourSix commented
Alright. Thanks.
SharkFourSix commented
sam commented
You may need to prefix the destination file to ensure the path is treated
as relative so it is moved into the workspace, i.e: ./README.pdf
…On Sun, 8 May 2022 at 20:17, SharkFourSix ***@***.***> wrote:
[image: image]
<https://user-images.githubusercontent.com/18681730/167312139-d04e105f-6660-4276-bfe3-12786d59d8b6.png>
I'm getting this error here. Where exactly does it save?
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACVL6JBLEIX7D7ZLXX6GC3VJAHNFANCNFSM5VMJL2JA>
.
You are receiving this because you commented.Message ID:
***@***.***>
SharkFourSix commented
Same thing. Permission denied. I noticed there are also two "//", indicating a missing directory entry.
Oh well