Sync Community Fork

A GitHub Actions workflow automatically pushes every commit on main and release-* branches to the hypershift-community/hypershift fork.

How It Works

The workflow is defined in .github/workflows/sync-community-fork.yaml. On every push to main or any release-* branch it checks out the repository using a fine-grained Personal Access Token (PAT) and pushes the triggering branch to the community fork. The PAT is used instead of the default GITHUB_TOKEN because the latter only has access to the source repository.

Because the push target is derived from github.ref_name, no hardcoded branch list or API queries are needed — end-of-life release branches simply stop receiving pushes and are no longer synced.

Configuration

The workflow requires one secret configured at the repository level:

Creating the Token

1. Go to Settings > Developer settings > Personal access tokens > Fine-grained tokens.
2. Click Generate new token.
3. Set Resource owner to the hypershift-community organization.
4. Under Repository access, select Only select repositories and choose hypershift-community/hypershift.
5. Grant no organization permissions.
6. Grant the following repository permissions:
7. Metadata — Read
8. Contents — Read and write
9. Pull requests — Read and write
10. Workflows — Read and write
11. Click Generate token and copy the value.

Rotating the Token

1. Create a new token following the steps above.
2. Update the repository secret using one of the following options:

Option A — GitHub CLI:

gh secret set COMMUNITY_FORK_TOKEN --repo openshift/hypershift

This will prompt you to paste the new token value.

Option B — Web UI:

In the openshift/hypershift repository, go to Settings > Secrets and variables > Actions and update the COMMUNITY_FORK_TOKEN secret with the new token value.

1. Verify the workflow runs successfully on the next push to main or a release-* branch.
2. Delete the old token from your GitHub account.