-
Notifications
You must be signed in to change notification settings - Fork 89
Branch-specific Preview Environments via GitHub Pages for Each PR #82
Copy link
Copy link
Closed
Labels
good first issueGood for newcomersGood for newcomerslevel:advancedAdvanced task · 45 GSSoC pointsAdvanced task · 45 GSSoC pointstype:accessibilitytype:devopstype:featureNew feature or requestNew feature or requesttype:performancePerformance optimization or latency improvementPerformance optimization or latency improvementtype:refactortype:securitySecurity vulnerability or hardeningSecurity vulnerability or hardeningtype:testingUnit tests, integration tests, or test coverageUnit tests, integration tests, or test coverage
Metadata
Metadata
Assignees
Labels
good first issueGood for newcomersGood for newcomerslevel:advancedAdvanced task · 45 GSSoC pointsAdvanced task · 45 GSSoC pointstype:accessibilitytype:devopstype:featureNew feature or requestNew feature or requesttype:performancePerformance optimization or latency improvementPerformance optimization or latency improvementtype:refactortype:securitySecurity vulnerability or hardeningSecurity vulnerability or hardeningtype:testingUnit tests, integration tests, or test coverageUnit tests, integration tests, or test coverage
🚀 Feature Request: Per-PR Preview Environments on GitHub Pages
Problem
Currently, reviewing and QA-ing a Pull Request requires contributors and reviewers to clone the repo, set up the local build environment (CMake, dependencies, etc.), and manually run the project. This creates a significant barrier — especially for non-core contributors or reviewers who just want to verify UI/UX changes.
Proposed Solution
Set up a CI/CD workflow (using GitHub Actions) that automatically builds and deploys a branch-specific preview environment to GitHub Pages for every open PR.
Each PR would get its own preview URL, something like:
When the PR is merged or closed, the preview is automatically torn down.
Implementation Idea
.github/workflows/preview.yml) triggered onpull_requesteventsgh-pagesbranch under a PR-specific subdirectoryBenefits
References