Multiple docs versions about yadism

[alecandido]

Strategy for multiple goals

develop docs

First choose one of the following:

1. Write a new workflow to run from develop branch only
2. Use the variable GITHUB_REF to separate from master

Than set the TARGET_FOLDER variable in the github-pages-deploy-action, by:

1. choosing your favourite name for develop docs
2. use a conditional github expression, e.g.:

          TARGET_FOLDER: ${{ github.ref }}

or

      - name: Deploy 🚀
        if: github.ref == 'master'
        uses: JamesIves/github-pages-deploy-action@releases/v3
        with:
          TARGET_FOLDER: ${{ github.ref }}
      - name: Deploy 🚀
        if: github.ref == 'develop'
        uses: JamesIves/github-pages-deploy-action@releases/v3
        with:
          TARGET_FOLDER: "dontrelymeimunstable"

version docs only

if using the strategy 1. try using 2. for the master only workflow, i.e. use TARGET_FOLDER: ${{ github.ref }}

redirect

put a redirect (maybe an HTML one) from base domain to /stable, not to be updated never by any workflow (nor deleted)

navigate docs version

Something like this:

[alecandido]

Since the content of ${{ github.ref }} is too raw, and it's not possible to elaborate the string directly in TARGET_FOLDER field, nor it's possible to use anything else, move to a completely different action, add-and-commit, to make the workflow more flexible.

Summary: instead of using a specific "deploying" action, just use a generic "commit" action and load manually the file in the gh-pages branch with git

(git is more flexible and reliable than a specific action)

[felixhekhorn]

stable branch is recovered