Skip to content

chore: sync master → development #222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
iannbing merged 2 commits into from
Apr 21, 2026
Merged

chore: sync master → development #222

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b53fe6b
Merge pull request #221 from iannbing/development
iannbing Apr 21, 2026
71a33d3
ci(docs): drop self-flip step — GITHUB_TOKEN can't call Pages admin API
iannbing Apr 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 8 additions & 12 deletions .github/workflows/docs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,18 +28,14 @@ jobs:
steps:
- uses: actions/checkout@v4

# The repo's Pages source used to be the `gh-pages` branch
# (legacy Storybook publish). `actions/deploy-pages` requires the
# source to be `workflow`, so idempotently flip it before we do
# anything else. The PUT is a no-op once the setting is already
# `workflow` — safe to run on every deploy.
- name: Ensure Pages is configured for Actions-based deploys
working-directory: .
run: |
gh api -X PUT "repos/${{ github.repository }}/pages" \
-F build_type=workflow
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# Pages `build_type` must be `workflow` for `actions/deploy-pages`
# to accept artifacts. That setting is flipped via the repo
# owner once (Settings → Pages → Source: GitHub Actions) or with
# `gh api -X PUT repos/<owner>/<repo>/pages -F build_type=workflow`
# from an admin-authed gh CLI. The workflow can't flip it itself:
# `GITHUB_TOKEN` with `pages: write` is enough to DEPLOY, but the
# Pages admin API (PUT /pages) requires repo-admin scope, which
# the workflow token doesn't carry.

- uses: actions/setup-node@v4
with:
Expand Down
Loading