-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Build process disrupted by mkdocs tags_file #1425
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
Comments
I've removed that deprecated option, and used the new correct syntax for the tag index. |
Unfortunately,when I've rerun build (when I could), it still fails. |
@jxu @mhayter Why rerunning some builds doesn't work automatically, is due to technical decisions by Github. The build step doesn't automatically use the code from the That sounds a bit odd. Especially when you come from other Code Versioning / DevOps platforms. E.g. I currently work a lot with Azure DevOps, and there the build always runs on the merge between the most recent target branch and your PR branch. Anyway. There are two easy solutions. Or alternatively close and reopen the PR (which is nicer to the creator of the PR, as they will not have additional commits in their Fork/Branch): |
Config value 'plugins': Plugin 'material/tags' option 'tags_file': This setting is not required anymore
@adamant-pwn @jakobkogler
The text was updated successfully, but these errors were encountered: