Conversation
kescobo
approved these changes
Jan 13, 2026
Member
|
🚀 |
Collaborator
Author
|
Looks like that did not fix the issue because I'm still getting the error.
but at least this narrows down what the problem is.
…On Tue, Jan 13, 2026, 12:59 PM Kevin Bonham ***@***.***> wrote:
*kescobo* left a comment (BioJulia/biojulia.github.io#26)
<#26 (comment)>
🚀
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZ5XYWMQ5WKSZHVICZUW6GT4GUXBZAVCNFSM6AAAAACRSIP5ROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONBVGY3DGNRUGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I was playing around with different variables in
make.jlto try to fix the deployment problem. I was testing out the changes by deploying the website locally. However, I noticed that once the hardcoding ofmd_output_path=""was removed from the deployment function, the website was generated correctly (it looks like issues with defining where the output file is generated has caused us trouble in the past https://github.com/BioJulia/BioJuliaDocs/pull/23/files) . Can we try merging this PR in and seeing if the website still fails to deploy correctly? If so, I think the next thing will be to investigate how Github is publishing the site, as it works locally.The Vitepress documentation does not explicitly set
md_output_pathin its example. https://luxdl.github.io/DocumenterVitepress.jl/stable/manual/documenter_to_vitepress_docs_example