Why is the deploying to gh-pages handled using the deploy.sh file and not through github actions?

[bahdotsh]

Is there any specific reason why slate is sticking with deploy.sh and not the github actions?
I wanted to start this discussion to understand the rationale behind this approach and potentially explore alternative deployment methods.

[MasterOdin]

Both should be supported and documented. In our docs for publishing slate, the final section is on publishing with github actions, which mostly just links to the GH workflow we use within this repo itself. Granted, this is after the initial block which talks about deploy.sh, though there is a note about looking below for CI.

Are you asking us to reword this page to more heavily advertise using GH actions, or are you looking somewhere else?

[MasterOdin]

I'm totally fine more heavily promoting using CI to deploy, and documenting how to do it more prominently, given that that's how we publish our example site ourselves within this repo, and would be a bit weird to push ./deploy.sh more heavily over what we ourselves do.

[bahdotsh]

Thank you for pointing me towards this, I actually kind of missed out on the gh-actions deploy section in the document!