Morten Piibeleht

I think I'm happy with the approach here. I'll aim to take a closer look at the implementation tomorrow. Having a test that at least runs the codepath would be...

Like in https://github.com/JuliaDocs/Documenter.jl/pull/2431#issuecomment-1925208280, it would be good to have a test here that would also run on Windows. Modifying the `texonly` test should be sufficient. Note: you should be able...

Yeah, this would be good to have in the manual somewhere. What I usually do is the following, if you have the standard setup with `docs/Project.toml`: ``` $ julia --project=docs/...

@Nauss `pkg> dev` is relative to the current working directory and the example above assumes you're in the parent directory of `MyProject`. In your case, as you're already in `MyProject/`,...

I think my preference would be to have it as a separate script (but one that we could definitely auto-generate for the user). I'd prefer not to re-run all the...

This looks interesting! I'll try to find some time to play with it properly. Would be awesome to also get more eyes on this, to see what people this about...

> I was not aware of the choice of Documenter plugins! Just to maybe clarify -- Documenter plugins are not a thing that strictly exist as a feature (yet; I...

I believe this requires some new token configuration before it can be merged. Edit: https://discourse.julialang.org/t/psa-new-version-of-codecov-action-requires-additional-setup/109857

I have also been experimenting with Coveralls a bit: https://coveralls.io/github/JuliaDocs/Documenter.jl I don't remember if there were any outstanding issues or not. It looks like #2343 might have fixed itself..

@goerz Since we went to v4 in https://github.com/JuliaDocs/ANSIColoredPrinters.jl/pull/18, I added the org-global token (which I enabled for all the Julia package repos we have right now). It looks like stuff...