ci: publish to master instead of GitHub Pages

nodejs.jp turns out to be served by Netlify out of the master branch, not
by GitHub Pages, so deploying through the Pages API would not touch the
live site. Replace the Pages deploy job with one that builds into a
checkout of master and pushes, which is what update.sh did under
CircleCI.

Author: kt3k

.github/workflows/deploy.yml

@@ -11,7 +11,7 @@ permissions:
 
 # Let a running deploy finish rather than cancelling it half way.
 concurrency:
-  group: pages
+  group: deploy
   cancel-in-progress: false
 
 jobs:
@@ -27,20 +27,42 @@ jobs:
       - run: npm run build
       # Uploaded on pull requests too, so the built site can be downloaded
       # from the run page for review.
-      - uses: actions/upload-pages-artifact@v5
+      - uses: actions/upload-artifact@v7
         with:
+          name: site
           path: build
 
+  # nodejs.jp is served by Netlify out of the master branch, so publishing
+  # means committing the build output there. This mirrors the update.sh that
+  # CircleCI used to run.
   deploy:
     needs: build
     if: github.event_name != 'pull_request'
     runs-on: ubuntu-latest
     permissions:
-      pages: write
-      id-token: write
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
+      contents: write
     steps:
-      - id: deployment
-        uses: actions/deploy-pages@v5
+      - uses: actions/checkout@v7
+      - uses: actions/setup-node@v7
+        with:
+          node-version-file: .node-version
+          cache: npm
+      - run: npm ci
+      - name: Check out master as the build destination
+        run: |
+          git clone --depth 1 -b master \
+            "https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}.git" \
+            build
+      - run: npm run build
+      - name: Commit and push
+        working-directory: build
+        run: |
+          git config user.name 'github-actions[bot]'
+          git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
+          git add -A
+          if git diff --cached --quiet; then
+            echo 'nothing to publish'
+            exit 0
+          fi
+          git commit -m 'chore(site): automated update from github actions'
+          git push origin HEAD:master

bulbofile.js

@@ -131,5 +131,6 @@ asset('source/pdfs/**/*.pdf')
 // Old site is available under http://nodejs.jp/old/
 asset('./old/*.*').base('./')
 
-// The custom domain needs to be part of the published artifact
+// Keep CNAME in the published output rather than relying on the copy that
+// happens to sit in master
 asset('./CNAME').base('./')