refactoring (currently per branch availability) #80

The root URL, i.e https://fabien.benetou.fr/pub/home/future_of_text_demo/engine/ , can get access a branch by appending branch_BRANCHNAME.html to it.

For example the branch book branch is available via https://fabien.benetou.fr/pub/home/future_of_text_demo/engine/branch_book.html

This is done via

echo "<html><ul>" > branches.html
for B in $(git branch --format "%(refname)"|sed "s/.*\///")
do
    git checkout $B
    cp index.html branch_$B.html
    echo "<li><a href=branch_$B.html>$B</a></li>" >> branches.html
done
echo "</ul></html>" >> branches.html
git checkout master;

in the per_branch_publish script.

This has not been tested thorougly.

This could become a commit/push hook.

Consider also a link from a specific branch to the root URL, e.g ln -s index.html branch_BRANCHAME.html.

If there is a dedicated publish step though might as well consider a separate directory or even domain.

See https://fabien.benetou.fr/pub/home/future_of_text_demo/engine/branches.html from updated script to add index.

Note that as discussed during the FOSDEM 1st preparation session, not everything in from all branches need to be merged back into master in order for refactoring to be useful. Even features that do not make it right away remain available for future integration. Consequently what is less daunting is refactoring through branches done by priority, and thus question what is core. See e.g #52 and https://git.benetou.fr/utopiah/text-code-xr-engine/issues?labels=26

Now an immersive page as shown in https://mastodon.pirateparty.be/@utopiah/109728712511418060

Requires a bit of manual work as equirectangular screenshots are manually generated.

Consider new actions https://blog.gitea.io/2023/03/gitea-1.19.0-is-released/#-gitea-actions-21937httpsgithubcomgo-giteagiteaissues21937

Consider minimalist pedagogical refactoring to be able to show how it works even to kids.

Consider runner too, cf https://gitea.com/gitea/act_runner