refactoring (currently per branch availability) #80
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.htmlto it.For example the branch
bookbranch is available via https://fabien.benetou.fr/pub/home/future_of_text_demo/engine/branch_book.htmlThis is done via
in the
per_branch_publishscript.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
Consider trying https://codeberg.org/coderofsalvation/forgejo-pages-diy