It may be that your docs/Project.toml must not reference the package itself. At least it is not in some non-registered packages I have, and I can see that if it was an error like that could occur.
Okay, but how will the workflow find the unregistered MFF package if I don’t add it as a dependency?
After all, I interpret your comment as follows:
I should remove the MFF dependency from the Project.toml file in the /docs dir.
Maybe you can “Pkg.dev” your package with a relative path instead?
Can you please clarify?
I’ve already added the package in dev mode using ] dev <LINK_TO_THE_PACKAGE>.
What I can say is that, for instance, the JuliaNotes.jl doesn’t have that. Another package I have doesn’t even have a Project.toml file in the docs folder, so I’m not sure what exactly is it for. I don’t have doc tests in those packages, though.
I usually follow very strictly that step by step and it works. Starting by generating the package with PkgTemplates.
I found that sometimes the gh-pages branch is not automatically created as described in the documenter.jl documentation , and needs to be created manually as described here, and commit to the main branch again to trigger the ci update.
I leave a comment here for someone encounter same problem