Feat: Add new workflow for publish docs #2018
Merged
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
bartekpacia
approved these changes
Nov 28, 2024
Juneezee
reviewed
Nov 29, 2024
There was a problem hiding this comment.
The latest publish job failed.
https://github.com/urfave/cli/actions/runs/12075203049/job/33674585639
go run scripts/build.go deploy-mkdocs
# ---> /usr/bin/git rev-parse --show-toplevel
# ---> /home/runner/.local/bin/mkdocs gh-deploy --force
Error: MkDocs encountered an error parsing the configuration file: while constructing a Python object
cannot find module 'material.extensions.emoji' (No module named 'material.extensions')
in "/home/runner/work/cli/cli/mkdocs.yml", line 9[5](https://github.com/urfave/cli/actions/runs/12075203049/job/33674585639#step:5:6), column 20
exit status 1
I think the error is introduced in this commit adccc52?
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.
What type of PR is this?
(REQUIRED)
What this PR does / why we need it:
(REQUIRED)
New workflow to publish docs separately from test
Which issue(s) this PR fixes:
(REQUIRED)
Special notes for your reviewer:
(fill-in or delete this section)
Testing
(fill-in or delete this section)
Release Notes
(REQUIRED)