We tried to follow GitHub’s new best practices and renamed master to main in Trixi.jl. We also changed all occurrences of master to main, e.g. in the setup of Documenter.jl and other GitHub actions. Currently, Documenter builds fine on pushes to main and deploys dev docs correctly. However, Documenter is not triggered anymore when a new tag/release is created. We are still using TagBot with DOCUMENTER_KEY as before.
Our current setup for Documenter:
name: Documentation
on:
push:
branches:
- 'main'
tags: '*'
pull_request:
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: julia-actions/setup-julia@latest
with:
version: '1.5'
- name: Install dependencies
run: julia --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd())); Pkg.instantiate()'
- name: Build and deploy
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # For authentication with GitHub Actions token
DOCUMENTER_KEY: ${{ secrets.DOCUMENTER_KEY }} # For authentication with SSH deploy key
run: julia --project=docs --color=yes docs/make.jl
Our current setup for TagBot:
name: TagBot
on:
issue_comment:
types:
- created
workflow_dispatch:
jobs:
TagBot:
if: github.event_name == 'workflow_dispatch' || github.actor == 'JuliaTagBot'
runs-on: ubuntu-latest
steps:
- uses: JuliaRegistries/TagBot@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
ssh: ${{ secrets.DOCUMENTER_KEY }}
Do you have an idea how to fix the issue and get new builds of the stable docs when a new release is tagged via TagBot?
Edit: Another slightly related question: Is there a simple way to add the dropped releases v0.3.14, v0.3.15, v0.3.16 to the gh-pages branch?