Create GHA workflow for altdoc

[etiennebacher]

Close #66

Very much WIP, just the skeleton for now

TODO:

• use r2u
• check if installing the package quarto is enough or if we need to setup Quarto: https://github.com/quarto-dev/quarto-actions/tree/main/setup

[netlify]

✅ Deploy Preview for upbeat-hamilton-47df84 ready!

Name	Link
🔨 Latest commit	72a485e
🔍 Latest deploy log	https://app.netlify.com/sites/upbeat-hamilton-47df84/deploys/655fbad5e13ff60008b5c8b0
😎 Deploy Preview	https://deploy-preview-122--upbeat-hamilton-47df84.netlify.app/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[vincentarelbundock]

This assumes we want to create an all new website every time, with no customization at all?

[vincentarelbundock]

How about setup_workflow()?

[etiennebacher]

Quarto installation fails because sudo: command not found. @vincentarelbundock do you think it's because we use a rocker container?

[vincentarelbundock]

No idea, which is why I use the script linked above ;)

[etiennebacher]

quarto-dev/quarto-actions#12

There are cases where install-quarto action can't be used (like in docker containers runners).

[etiennebacher]

The CI went through, need to see how it goes after we merge this. Need to update function name, docs, CI template first

[vincentarelbundock]

this is cool

[vincentarelbundock]

Out of curiosity, what is the benefits of pushing to a separate branch vs. just loading it directly from docs/ in main?

[etiennebacher]

this is cool

yes but it still doesn't work because git is not installed / badly configured in the container. I'm exploring now

Out of curiosity, what is the benefits of pushing to a separate branch vs. just loading it directly from docs/ in main?

After a you merge a PR / push some commits, you don't need to pull again to import locally the changes in the docs folder