Skip to content

docs: Document single-PR deployment limitation and production workaround #622

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

Draft
Copilot wants to merge 2 commits into
base: ci-fix
Choose a base branch
from
Draft

docs: Document single-PR deployment limitation and production workaround #622

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d7107ca
Initial plan
Copilot Feb 5, 2026
9e1bbab
docs: Clarify single-PR deployment limitation in README
Copilot Feb 5, 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
11 changes: 11 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,7 @@ The FORRT website uses a dual deployment strategy to ensure quality and enable c
- **Trigger**: Pull requests to `master`, monthly schedule (1st of each month), or manual dispatch
- **Target**: External repository (`forrtproject/webpage-staging`)
- **Purpose**: Preview combined changes from all open PRs
- **Note**: Staging always deploys aggregated changes from all open PRs. There is currently no option to deploy a single PR in isolation to staging.

#### How Staging Works

Expand Down Expand Up @@ -108,6 +109,16 @@ The staging deployment uses an **aggregation strategy** to provide a unified pre
- Note: Staging shows aggregated changes from **all** open PRs, not individual PR changes
- PRs with merge conflicts won't appear in staging until conflicts are resolved

#### Manual Single-PR Deployment

**Currently Not Supported for Staging**: There is no option to deploy a single PR in isolation to the staging environment. All staging deployments include all compatible open PRs.

**Workaround for Testing Individual PRs**:
- The `deploy.yaml` workflow supports manual dispatch with a `pr_number` input
- However, this deploys directly to **production** (forrt.org), not staging
- Use with extreme caution - only for emergency fixes or when you're certain the changes are ready for production
- For regular PR testing, rely on the aggregated staging deployment or test locally

#### Monthly Reports

On the 1st of each month, an automated deployment report is created as a GitHub issue with:
Expand Down