🌿 sync-openapi

A GitHub Action to sync OpenAPI specifications with your Fern setup. Choose your scenario:

• Case 1: Sync from public URL (most common). Your OpenAPI spec is hosted at a publicly available URL and you want to pull it into your fern folder. The GitHub Action uses fern api update to pull the latest version of your OpenAPI spec from the origin field in your generators.yml file.
• Case 2: Sync between repositories: Your OpenAPI spec lives in one repository and you want to sync it to another repository where your fern folder lives (like fern-config). The GitHub Action uses explicit file mappings to pull the latest version of your OpenAPI spec.

Usage

Case 1: Sync specs from public URL (recommended)

1. In your repo, create a file named sync-openapi.yml in .github/workflows/.
2. Include the following contents in sync-openapi.yml:

name: Sync OpenAPI Specs # can be customizedon: # additional custom triggers can be configured, examples belowworkflow_dispatch: # manual dispatchpush: branches:
- main # on push to mainschedule:
- cron: '0 3 * * *'# everyday at 3:00 AM UTCjobs:
update-from-source:
runs-on: ubuntu-lateststeps:
- uses: actions/checkout@v4with:
token: ${{ secrets.OPENAPI_SYNC_TOKEN }}
- name: Update API with Fernuses: fern-api/sync-openapi@v4with:
update_from_source: truetoken: ${{ secrets.OPENAPI_SYNC_TOKEN }}auto_merge: false # you MUST use auto_merge: true with branch: main

PR deduplication: When auto_merge is false, the action creates a single PR on the branch (default: fern/sync-openapi) and accumulates commits on subsequent runs. If the source spec hasn't changed, the action is a no-op. This prevents duplicate PRs from piling up.

Branch divergence handling: If the PR branch has diverged (e.g., someone manually rebased or edited it), the action will attempt to rebase automatically. If rebase fails due to merge conflicts, a comment is left on the PR with detailed error output and resolution steps.

Case 2: Sync files/folders between repositories

1. In your source repo, create a file named sync-openapi.yml in .github/workflows/.
2. Include the following contents in sync-openapi.yml:

name: Sync OpenAPI Specs # can be customizedon: # additional custom triggers can be configured, examples belowworkflow_dispatch: # manual dispatchpush: branches:
- main # on push to mainschedule:
- cron: '0 3 * * *'# everyday at 3:00 AM UTCjobs:
sync:
runs-on: ubuntu-lateststeps:
- uses: actions/checkout@v4
- name: Sync OpenAPI spec to target repouses: fern-api/sync-openapi@v4with:
repository: <your-org>/<your-target-repo>token: ${{ secrets.<PAT_TOKEN_NAME> }}sources: # all paths are relative to source repository root
- from: path/to/source/dir # supports folder syncingto: path/to/target/dir exclude: # optional
- "path/to/file/to/exclude.yaml"# supports individual file exclusion
- "path/to/dir/to/exclude/**"# supports glob-based pattern matching
- "path/to/files/*_test.yaml"
- from: path/to/source/file.yaml # supports individual file syncingto: path/to/target/file.yaml ....branch: mainauto_merge: true # you MUST use auto_merge: true with branch: main

Inputs

Input	Description	Required	Default	Case
token	GitHub token for authentication	Yes	-	1, 2
branch	Branch name to create or update. Must be a stable name (e.g., fern/sync-openapi) — do not use dynamic/timestamped names, or PR deduplication will not work.	No	fern/sync-openapi	1, 2
auto_merge	If true, pushes directly to the branch; if false, creates a PR from the branch onto main	No	false	1, 2
sources	Array of mappings with from, to, and optional exclude fields	Yes	-	2
repository	Target repository in format org/repo	Yes	-	2
update_from_source	If true, runs fern api update on the current repository instead of syncing files between repos	No	false	1

Note: you must set auto_merge: true when using branch: main

Required Permissions

The GitHub token used for this action must have:

1. Read access to the source repository
2. Read/Write access to Contents and Pull requests for the repository being updated

Adding a Token for GitHub Actions

1. Generate a fine-grained https://github.com/settings/personal-access-tokens token with the above-mentioned permissions
2. Go to Settings -> Secrets and variables -> Actions and click on New repository secret
3. Name your token (i.e. OPENAPI_SYNC_TOKEN) and paste in the PAT token generated above
4. Replace <PAT_TOKEN_NAME> in the example YAML configuration with your token name.

Releasing

Tag the commit and publish a GitHub Release:

git tag v4.0.1
git push origin v4.0.1
gh release create v4.0.1 --generate-notes

The release workflow automatically moves the major and minor version tags (e.g. v4 and v4.0) to the new release so users pinned to @v4 or @v4.0 get the update immediately.

---