# The last step in publishing the docs

**URL:** <https://discourse.julialang.org/t/the-last-step-in-publishing-the-docs/23207>\
**Category:** New to Julia\
**Tags:** question, documentation\
**Created:** [April 16, 2019, 1:35pm UTC](https://discourse.julialang.org/t/the-last-step-in-publishing-the-docs/23207 "2019-04-16T13:35:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![leiteiro](https://avatars.discourse-cdn.com/v4/letter/l/b5e925/32.png) [@leiteiro](https://discourse.julialang.org/u/leiteiro)\
**Post date:** [April 16, 2019, 1:35pm UTC](https://discourse.julialang.org/t/the-last-step-in-publishing-the-docs/23207/1 "2019-04-16T13:35:49Z")

</div>

A miracle happened and my module, including the documentation, successfully passed through Travis. My joy is clouded just by the fact that I can’t find the documentation anywhere, at least not where I expect it to be published.

Instead, Travis tells me:

```
From github.com:Leitero/Coimbra.jl
* [new branch] master -> upstream/master
fatal: 'upstream/gh-pages' is not a commit and a branch 'gh-pages' 
cannot be created from it. Switched to a new branch 'gh-pages'
[gh-pages (root-commit) 40086dc]. Initial empty commit for docs.

```

But then Travis creates all the doc-files and says:

```
remote: Create a pull request for 'gh-pages' on GitHub by visiting:        
remote: https://github.com/Leitero/Coimbra.jl/pull/new/gh-pages

```

Indeed at this address there are the doc files and I am invited to “Compare changes”; on the other hand it tells me “There isn’t anything to compare. master and gh-pages are entirely different commit histories.”

Please help me: how do I get the docs through Travis to [leitero.github.io/Coimbra.jl/dev](http://leitero.github.io/Coimbra.jl/dev) where I expected them?

---

<div class="post-metadata">

**Author:** ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)\
**Post date:** [April 16, 2019, 2:38pm UTC](https://discourse.julialang.org/t/the-last-step-in-publishing-the-docs/23207/2 "2019-04-16T14:38:35Z")

</div>

Do you have a link to the Travis logs? Is the repository not public? [https://github.com/Leitero/Coimbra.jl](https://github.com/Leitero/Coimbra.jl) is a 404 for me. Did you enable gh-pages for the repo? If you go to [https://github.com/Leitero/Coimbra.jl/tree/gh-pages](https://github.com/Leitero/Coimbra.jl/tree/gh-pages) do you see the pushed files?

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [April 16, 2019, 2:56pm UTC](https://discourse.julialang.org/t/the-last-step-in-publishing-the-docs/23207/3 "2019-04-16T14:56:33Z")

</div>

[https://github.com/tpapp/skeleton.jl/tree/master/template](https://github.com/tpapp/skeleton.jl/tree/master/template)

has a working template for everything. Either compare your files to the template, or you can generate an example with the correct names and then just diff.

---

<div class="post-metadata">

**Author:** ![leiteiro](https://avatars.discourse-cdn.com/v4/letter/l/b5e925/32.png) [@leiteiro](https://discourse.julialang.org/u/leiteiro)\
**Post date:** [April 16, 2019, 8:07pm UTC](https://discourse.julialang.org/t/the-last-step-in-publishing-the-docs/23207/4 "2019-04-16T20:07:21Z")

</div>

After some more attempts the problem solved itself, unfortunately without me being able to say what exactly the error was. Many thanks for the help!

---

<div class="post-metadata">

**Author:** ![rdeits](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rdeits/32/286_2.png) [@rdeits](https://discourse.julialang.org/u/rdeits)\
**Post date:** [April 16, 2019, 8:42pm UTC](https://discourse.julialang.org/t/the-last-step-in-publishing-the-docs/23207/5 "2019-04-16T20:42:24Z")

</div>

Github pages updates are not always instantaneous–their servers can take some time to propagate your updates through to the public internet (and I’ve found that the speed at which this happens is pretty variable). It’s possible that you did everything right and github was simply being slow.