-
Notifications
You must be signed in to change notification settings - Fork 8
Make workflow-trigger
an input to download artifact step
#104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -75,7 +75,6 @@ jobs: | |||
uses: dawidd6/[email protected] | |||
with: | |||
github_token: ${{ secrets.GITHUB_TOKEN }} | |||
workflow: trigger-book-build.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this line is needed to identify the workflow that produced the artifact.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, so it doesn't start a new action. On the portal site, this isn't a workflow though. The workflow that produces the artifact will be in publish-site.yaml
. I'll try changing this to be an optional input with the trigger-book-build.yaml as its default value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That explains why the error on my fork say "Error: no matching workflow run found with any artifacts?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any other questions I have about the inputs to this step can be answered in the action-download-artifact
documentation 🤦♀️
workflow-trigger
an input to download artifact step
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks sensible to me @jukent !
I am unsure on why this step to trigger the build-build lives inside of the book-build. Let me know what you think.
E: Thanks @brian-rose for explaining that it doesn't trigger the trigger-book-build.yaml workflow, but tells the book-build action to look in that action for the artifact.
Related to ProjectPythia/projectpythia.github.io#415 and ProjectPythia/projectpythia.github.io#319