Fail to deploy from Documenter to GITHUB

I am working on Muscade.jl (work in progress!), and I have a first incomplete documentation I wish to deploy. Everything works fine… except I get a 404. Here is the dump:

My repo structure includes


My make.jl is

using Documenter, Muscade

repo = normpath((@__DIR__)*"/..")

makedocs(sitename ="Muscade.jl",
        format    = Documenter.HTML(prettyurls = false,
                                    sidebar_sitename = false),
        pages     = ["",
                     source  = "src",
                     build   = "build"   

deploydocs(repo = "",target="build",devbranch="philippe")

Muscade/.github/workflows/documentation.yml contains

name: Documentation
      - main
    tags: '*'

      contents: write
    runs-on: ubuntu-latest
      - uses: actions/checkout@v2
      - uses: julia-actions/setup-julia@v1
          version: '1.8'
      - name: Install dependencies
        run: julia --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd())); Pkg.instantiate()'
      - name: Build and deploy
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # If authenticating with GitHub Actions token
        #  DOCUMENTER_KEY: ${{ secrets.DOCUMENTER_KEY }} # If authenticating with SSH deploy key
        run: julia --project=docs/ docs/make.jl

In GITHUB | settings | pages, I have specified:
“deploy from a branch”, “main” “/root” and clicked save.

Building the doc locally works, I can navigate my doc.

I tag and commit a release, create an issue with “@juliaregistrator register”. The release goes well.
I point my browser to       

In the two first cases I get 404, in the later, I get to read my file.

It’s difficult to move on without any feedback on what the problem is. Any suggestions?

Try ‘gh-pages’ ?

Oh thanks, I had missed that! :grinning: So now I have set “deploy from a branch”, “gh-pages”.

That alone does not make the doc appear. What triggers the doc-deploying bot?

  1. A commit & push on my philippe dev-branch does not seem to do so.
  2. Does it have to be a create new issue | @juliaregistrator register-release,
  3. or a GITHUB | releases | Draft a new release?

One thing to mention - I’ve noticed delays of up to 30 minutes before the documentation finally appears, although on other occasions it works almost instantly. Makes trouble-shooting frustrating… :grinning:

That’s a very important point! “will be compiled by the server in the next round…”

My question on “what triggers the doc-deploying bot?” still stands. Anyone?

Probably a commit and push to a github action.

Docs look OK :joy:

1 Like

VICTORY !!! :grinning: :sunny:

Hey wait, I was too fast: on what URL did you obtain this vision of beauty? I still get 404 on all the above-mentionned URLs… Some get to see my docs :stuck_out_tongue:

1 Like

Cool! By the way, are you running an old version of Documenter?

Yes, since there’s no badge I went for Reference manual · Muscade.jl

How did you ever obtain that URL !?! :smile:`

I have (yesterday) created a series of commits in the hope of deploying - I am now at 0.3.5. So we are looking at an “old” doc (though the text hasn’t changed).

I was using [e30172f5] Documenter v0.27.24, and am now updating it.

Your built documents go here:

so just link to the github-pages bit and point to the folder you want.

There are three difficult parts to developing Julia packages: learning Git(hub), setting up Documenter, and - well, that’s it, really… :joy:


Ahh, now I will be able to see what is available.
Thank you for taking the time!

1 Like

A new GitHub release, afaik

I will test that a little later. But I feel that with your help and Cormullion, I am going to get grip on this. Thank you!

This is what I do, specifically: Publish Docs · JuliaNotes.jl

1 Like

Muito obrigado! I will read this very carefully!

1 Like