ci: generate pages artifact in Monty API Docs workflow #74
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tristanls
changed the title
tristanls
added
infrastructure
codeallthethingz
approved these changes
Nov 26, 2024
|
😄 I still don't know if it'll work 🤞. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After #73, I learned that the
actions/download-artifact@v4cannot find an artifact uploaded withactions/upload-pages-artifact@v3(or at least I haven't found a way to configure it correctly).This pull request uploads a "normal" Monty API Docs artifact via
actions/upload-artifact@v4, so thatactions/download-artifact@v4can find it. This "normal" artifact is then downloaded and the GitHub Pages artifact is created and uploaded in the Monty API Docs workflow and then deployed.