Commit initial files

[jburgy]

See zig-wasm/.github#1 for context.

[jburgy]

@Afirium I'm not even sure that approving this PR will run GitHub actions on it. I think you need to enable actions on the repo. Should be obvious when you visit the Settings ⚙. You might want to grab .github/workflows/deploy.yml and commit it

[jburgy]

I created a parallel jburgy/zorth#1 to test GitHub actions. Holy priceless collection of Etruscan snoods, Batman, it worked!

Unfortunately, GFM restrictions are dashing my hopes to add a cute demo to the README. I guess I'll record an interaction and add a GIF 😞

[Afirium]

Hey @jburgy, looks great! I enbled permissions for github pages in the settings. Btw I invited you as a member of the org, check your email. That way you can work on this repo without forks

[Afirium]

I pushed the yml file to the main branch, now you can try adding index.html to see if CI works in PR

[jburgy]

Accepting your invite does give me some additional permissions, @Afirium. Unfortunately...

[Afirium]

@jburgy 👍 you have access only to repository-level variables, not organization-level variables.
And now you can add index.html and test whether CI is working

[jburgy]

@Afirium this tells me that CI works as I expect it to, particularly these lines:

Archive artifact
  ./
  ./zorth.wasm
  ./zorth.mjs
  ./coi-serviceworker.min.js
  ./index.html

If you approve this PR, I can merge it which will deploy that artifact to <GitHub page URL>/zorth. I assume you've configured the pages to use zigwasm.org as a custom domain which is why README.md refers to https://zigwasm.org/zorth.

[jburgy]

@Afirium I did not notice that you approved the changes and committed more changes which invalidated your approval. Mind approving again pretty please?

[Afirium]

@jburgy great! After merge, I'll set up a cloudflare pages redirect to this domain, and add the project to the zigwasm.org homepage