deploy to gh-pages branch

Author: bakkot

.gitattributes

@@ -1,19 +1,15 @@
-name: Deploy spec
+name: Build spec
 
-on: [push]
+on: pull_request
 
 jobs:
   build:
     runs-on: ubuntu-latest
 
     steps:
     - uses: actions/checkout@v2
-    - uses: actions/setup-node@v1
+    - uses: actions/setup-node@v3
       with:
-        node-version: '12.x'
+        node-version: 16
     - run: npm install
     - run: npm run build
-    - name: commit changes
-      uses: elstudio/actions-js-build/commit@v3
-      with:
-        commitMessage: "fixup: [spec] `npm run build`"

.github/workflows/build.yml

@@ -0,0 +1,23 @@
+name: Deploy gh-pages
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - uses: actions/setup-node@v3
+      with:
+        node-version: 16
+    - run: npm install
+    - run: npm run build
+    - uses: JamesIves/[email protected]
+      with:
+        branch: gh-pages
+        folder: build
+        clean: true

.github/workflows/deploy.yaml

@@ -41,3 +41,6 @@ yarn.lock
 package-lock.json
 npm-shrinkwrap.json
 pnpm-lock.yaml
+
+# Build directory
+build

.gitignore

@@ -13,23 +13,11 @@ Please ensure the following:
 
 Follow these steps:
   1.  Click the green ["use this template"](https://github.com/tc39/template-for-proposals/generate) button in the repo header. (Note: Do not fork this repo in GitHub's web interface, as that will later prevent transfer into the TC39 organization)
-  1.  Go to your repo settings “Options” page, under “GitHub Pages”, and set the source to the **main branch** under the root (and click Save, if it does not autosave this setting)
+  1.  Go to your repo settings “Options” page, under “GitHub Pages”, and set the source to `gh-pages` under the root and click Save. You may need to wait a minute or so after creating the repo for the initial build to finish and create the branch.
       1. check "Enforce HTTPS"
       1. On "Options", under "Features", Ensure "Issues" is checked, and disable "Wiki", and "Projects" (unless you intend to use Projects)
       1. Under "Merge button", check "automatically delete head branches"
-<!--
-  1.  Avoid merge conflicts with build process output files by running:
-      ```sh
-      git config --local --add merge.output.driver true
-      git config --local --add merge.output.driver true
-      ```
-  1.  Add a post-rewrite git hook to auto-rebuild the output on every commit:
-      ```sh
-      cp hooks/post-rewrite .git/hooks/post-rewrite
-      chmod +x .git/hooks/post-rewrite
-      ```
--->
-  3.  ["How to write a good explainer"][explainer] explains how to make a good first impression.
+  1.  ["How to write a good explainer"][explainer] explains how to make a good first impression.
 
       > Each TC39 proposal should have a `README.md` file which explains the purpose
       > of the proposal and its shape at a high level.