retypeapp · geoffreymcgill · Feb 13, 2026
diff --git a/README.md b/README.md
@@ -2,28 +2,33 @@
 
 A GitHub Action to push a website built by [Retype](https://retype.com/) in a previous [`action-build`](https://github.com/retypeapp/action-build) step back to the GitHub repo where it can then be hosted by [GitHub Pages](https://docs.github.com/en/github/working-with-github-pages/getting-started-with-github-pages).
 
-This action includes options to push to a `branch`, or a `directory`, or automatically create a pull request which can then be reviewed and merged.
+This action includes options to publish by pushing to a `branch` or a `directory`, automatically create a pull request, or deploy directly to GitHub Pages when your repo is configured with Pages **Source: GitHub Actions**.
 
 ## Introduction
 
 This action will commit and push back a Retype website to a GitHub repo. The website will have been built during a previous step by using the [retypeapp/action-build](https://github.com/retypeapp/action-build) action.
 
 The following functionality is configurable by this action:
 
-1. Target a `branch`, or
-2. Target a `directory` in the repo
-3. Configure whether a new branch should be created if it already exists (`update-branch`)
-4. Configure a GitHub API access token to allow the action to make a Pull Request (`github-token`)
+1. Choose where to publish (`publish-to: branch` or `publish-to: pages`)
+2. Target a `branch` (branch mode), or
+3. Target a `directory` in the repo (branch mode)
+4. Configure whether a new branch should be created if it already exists (`update-branch`, branch mode)
+5. Configure a GitHub API access token to allow the action to make a Pull Request (`github-token`, branch mode)
 
 ## Prerequisites
 
 This action requires the output of the [retypeapp/action-build](https://github.com/retypeapp/action-build) in a previous step of the workflow.
 
+If you are using the new GitHub Pages publishing model (Pages **Source: GitHub Actions**), you must enable it in your repo first:
+
+- **Settings → Pages → Build and deployment → Source: GitHub Actions**
+
 Please see [Getting Started with GitHub Pages](https://docs.github.com/en/github/working-with-github-pages/getting-started-with-github-pages) for details on how to configure GitHub Pages.
 
 ## Usage
 
-The following `retype.yaml` file demonstrates a typical scenario where the action will trigger Retype to build when changes are pushed to the repo. The fresh Retype powered website is then pushed to a `retype` branch which has been setup in the repo settings to host with GitHub Pages.
+The following GitHub Actions workflow demonstrates a typical scenario where the action will trigger Retype to build when changes are pushed to the repo. The fresh Retype powered website is then pushed to a `retype` branch which has been set up in the repo settings to host with GitHub Pages.
 
 ```yaml
 name: Publish Retype powered website to GitHub Pages
@@ -52,8 +57,66 @@ jobs:
           update-branch: true
 ```
 
+### Publish using GitHub Pages Source: GitHub Actions
+
+If your repository is configured with **Pages Source: GitHub Actions**, you can deploy without pushing generated files to a branch.
+
+Key differences vs branch publishing:
+
+- Your workflow must grant `pages: write` and `id-token: write` permissions.
+- This action will upload a Pages artifact and then deploy it using the official GitHub Pages actions.
+
+```yaml
+name: Publish Retype powered website to GitHub Pages (GitHub Actions)
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pages: write
+      id-token: write
+    environment:
+      name: github-pages
+      url: ${{ steps.pages.outputs.page_url }}
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: retypeapp/action-build@latest
+
+      - id: pages
+        uses: retypeapp/action-github-pages@latest
+        with:
+          publish-to: pages
+```
+
+## Outputs
+
+### `page_url`
+
+The deployed GitHub Pages URL. Only set when `publish-to: pages` and `pages-deploy` is not `false`.
+
+### `artifact_id`
+
+The uploaded Pages artifact ID. Only set when `publish-to: pages`.
+
 ## Inputs
 
+### `publish-to`
+
+Controls where the Retype output is published.
+
+- **Default:** `branch`
+- **Accepts:** `branch` or `pages`
+
+When set to `pages`, the branch-related inputs (`branch`, `directory`, `update-branch`, `github-token`) are ignored.
+
 ### `branch`
 
 Specifies the target branch where the Retype output will be merged.
@@ -104,9 +167,39 @@ Specifies a GitHub Access Token that enables the action to make a pull request w
 
 The action will never use the access token if (1) the branch does not exist, (2) `update-branch` is configured, or (3) if `branch: HEAD` is specified.
 
+### `pages-path`
+
+Only used when `publish-to: pages`.
+
+- **Default:** `${RETYPE_OUTPUT_PATH}` (set by `retypeapp/action-build`)
+- **Accepts:** a string path
+
+### `pages-artifact-name`
+
+Only used when `publish-to: pages`.
+
+- **Default:** `github-pages`
+- **Accepts:** a string
+
+### `pages-retention-days`
+
+Only used when `publish-to: pages`.
+
+- **Default:** `1`
+- **Accepts:** a number (days)
+
+### `pages-deploy`
+
+Only used when `publish-to: pages`.
+
+- **Default:** `true`
+- **Accepts:** `true` or `false`
+
+If set to `false`, the action will only upload the Pages artifact. You can then deploy it in a separate job using `actions/deploy-pages`.
+
 ## Examples
 
-The following `retype.yaml` workflow file will serve as our starting template for most of the samples below.
+The following GitHub Actions workflow will serve as our starting template for most of the samples below.
 
 ```yaml
 name: Publish Retype powered website to GitHub Pages

diff --git a/action.yml b/action.yml
@@ -1,8 +1,15 @@
 name: Retype Action for GitHub Pages
 author: Object.NET, Inc.
 description: |-
-  Publishes a Retype website to a branch, directory, or creates a pull request.
+  Publishes a Retype website to a branch/directory (optionally via pull request), or deploys to GitHub Pages using a GitHub Actions workflow.
 inputs:
+  publish-to:
+    description: |-
+      Where to publish the Retype output.
+      - branch (default): Commit/push to a target branch/directory (existing behavior).
+      - pages: Deploy to GitHub Pages when the repo Pages source is set to "GitHub Actions".
+    required: false
+    default: branch
   branch:
     description: |-
       The name of the target branch where the Retype output will be committed. 
@@ -28,13 +35,84 @@ inputs:
       branch will be created. If this option is not set, the action may push a 
       new branch but will not create a pull request. Default is empty.
     required: false
+
+  pages-path:
+    description: |-
+      Only used when publish-to=pages.
+      Path to the directory containing the static assets to deploy.
+      Defaults to the RETYPE_OUTPUT_PATH environment variable set by retypeapp/action-build.
+    required: false
+  pages-artifact-name:
+    description: |-
+      Only used when publish-to=pages.
+      Artifact name to upload for GitHub Pages deployment.
+    required: false
+    default: github-pages
+  pages-retention-days:
+    description: |-
+      Only used when publish-to=pages.
+      How long (in days) to keep the uploaded Pages artifact.
+    required: false
+    default: '1'
+  pages-deploy:
+    description: |-
+      Only used when publish-to=pages.
+      If true (default), the action will deploy to GitHub Pages.
+      If false, the action will only upload the Pages artifact.
+    required: false
+    default: 'true'
+
+outputs:
+  page_url:
+    description: The GitHub Pages URL (only set when publish-to=pages and pages-deploy=true).
+    value: ${{ steps.pages_deploy.outputs.page_url }}
+  artifact_id:
+    description: The uploaded Pages artifact ID (only set when publish-to=pages).
+    value: ${{ steps.pages_upload.outputs.artifact_id }}
 runs:
   using: "composite"
   steps:
-    - run: "${GITHUB_ACTION_PATH}/github.sh"
+    - name: Publish to branch/directory
+      if: ${{ inputs.publish-to != 'pages' }}
+      run: "${GITHUB_ACTION_PATH}/github.sh"
       shell: bash
       env:
         INPUT_BRANCH: ${{ inputs.branch }}
         INPUT_DIRECTORY: ${{ inputs.directory }}
         INPUT_UPDATE_BRANCH: ${{ inputs.update-branch }}
-        INPUT_GITHUB_TOKEN: ${{ inputs.github-token }}
+        INPUT_GITHUB_TOKEN: ${{ inputs.github-token }}
+
+    - name: Validate Retype output path
+      if: ${{ inputs.publish-to == 'pages' }}
+      shell: bash
+      env:
+        PAGES_PATH: ${{ inputs.pages-path != '' && inputs.pages-path || env.RETYPE_OUTPUT_PATH }}
+      run: |
+        if [ -z "${PAGES_PATH}" ]; then
+          echo "::error::Retype output path is not defined. Run retypeapp/action-build (or set pages-path)."
+          exit 1
+        fi
+        if [ ! -d "${PAGES_PATH}" ]; then
+          echo "::error::Unable to locate static site directory: ${PAGES_PATH}"
+          exit 1
+        fi
+
+    - name: Configure GitHub Pages
+      if: ${{ inputs.publish-to == 'pages' }}
+      uses: actions/configure-pages@v5
+
+    - name: Upload Pages artifact
+      id: pages_upload
+      if: ${{ inputs.publish-to == 'pages' }}
+      uses: actions/upload-pages-artifact@v3
+      with:
+        path: ${{ inputs.pages-path != '' && inputs.pages-path || env.RETYPE_OUTPUT_PATH }}
+        name: ${{ inputs.pages-artifact-name != '' && inputs.pages-artifact-name || 'github-pages' }}
+        retention-days: ${{ inputs.pages-retention-days != '' && inputs.pages-retention-days || 1 }}
+
+    - name: Deploy to GitHub Pages
+      id: pages_deploy
+      if: ${{ inputs.publish-to == 'pages' && inputs.pages-deploy != 'false' }}
+      uses: actions/deploy-pages@v4
+      with:
+        artifact_name: ${{ inputs.pages-artifact-name != '' && inputs.pages-artifact-name || 'github-pages' }}