# Documenter.jl failed to build on a GitHub action, how can I run locally commit to gh-pages?

**URL:** <https://discourse.julialang.org/t/documenter-jl-failed-to-build-on-a-github-action-how-can-i-run-locally-commit-to-gh-pages/104579>\
**Category:** General Usage\
**Tags:** question\
**Created:** [October 4, 2023, 4:23pm UTC](https://discourse.julialang.org/t/documenter-jl-failed-to-build-on-a-github-action-how-can-i-run-locally-commit-to-gh-pages/104579 "2023-10-04T16:23:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![haberdashPI](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/haberdashpi/32/26337_2.png) [@haberdashPI](https://discourse.julialang.org/u/haberdashPI)\
**Post date:** [October 4, 2023, 4:23pm UTC](https://discourse.julialang.org/t/documenter-jl-failed-to-build-on-a-github-action-how-can-i-run-locally-commit-to-gh-pages/104579/1 "2023-10-04T16:23:11Z")

</div>

What is the simplest way to build docs with Documenter.jl locally and push the appropriate updates to `gh-pages`? When I build locally I get

```sh
┌ Warning: Documenter could not auto-detect the building environment Skipping deployment.
└ @ Documenter ~/.julia/packages/Documenter/9kOxY/src/deployconfig.jl:76

```

But is there some way to set `deploy_config` for `deploydocs` so that it adds a commit to `gh-pages` locally and I can manually push that to GitHub? I want to do this for a tagged release v0.1.0.

I didn’t have the right environment variables set up so my CI GitHub Actions did not deploy my Documenter.jl docs. That’s been fixed, but I’m wondering if there is someway to manually build the docs so that I have some docs under v0.1.0. (Since the tag v0.1.0 has already been added).

Alternatively if there is some way to manually trigger the appropriate GitHub action for the release that would also work for me.

---

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [October 4, 2023, 4:26pm UTC](https://discourse.julialang.org/t/documenter-jl-failed-to-build-on-a-github-action-how-can-i-run-locally-commit-to-gh-pages/104579/2 "2023-10-04T16:26:02Z")

</div>

You can just check out your `gh-pages` branch in a separate folder and copy the `build` folder there and commit & push it

---

<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:** [October 4, 2023, 4:32pm UTC](https://discourse.julialang.org/t/documenter-jl-failed-to-build-on-a-github-action-how-can-i-run-locally-commit-to-gh-pages/104579/3 "2023-10-04T16:32:01Z")

</div>

> [@haberdashPI](#):
>
> I want to do this for a tagged release v0.1.0.

Perhaps you are interested in [Fixing broken release deployments](https://documenter.juliadocs.org/stable/man/hosting/#Fixing-broken-release-deployments).

---

<div class="post-metadata">

**Author:** ![haberdashPI](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/haberdashpi/32/26337_2.png) [@haberdashPI](https://discourse.julialang.org/u/haberdashPI)\
**Post date:** [October 4, 2023, 4:33pm UTC](https://discourse.julialang.org/t/documenter-jl-failed-to-build-on-a-github-action-how-can-i-run-locally-commit-to-gh-pages/104579/4 "2023-10-04T16:33:45Z")

</div>

Oh, thank you! Missed that. I’ll give that a try.