fix(ci): Consolidate staging deployments and prevent duplicate builds#617
fix(ci): Consolidate staging deployments and prevent duplicate builds#617richarddushime wants to merge 7 commits intomasterfrom
Conversation
✅ Spell Check PassedNo spelling issues found in this PR! 🎉 |
|
👍 All image files/references (if any) are in webp format, in line with our policy. |
|
✅ Staging Deployment Status This PR has been successfully deployed to staging as part of an aggregated deployment. Deployed at: 2026-02-06 13:44:09 UTC The staging site shows the combined state of all compatible open PRs. |
|
@LukasWallrich Good to go but i will keep monitoring it |
|
@copilot please review and document the approach to staging in the README |
|
@LukasWallrich I've opened a new pull request, #621, to work on those changes. Once the pull request is ready, I'll request review from you. |
* Initial plan * docs: Document staging deployment approach in README Co-authored-by: LukasWallrich <60155545+LukasWallrich@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: LukasWallrich <60155545+LukasWallrich@users.noreply.github.com>
✅ Spell Check PassedNo spelling issues found in this PR! 🎉 |
|
@copilot there should be an option to manually deploy a single PR to staging (which seems to be implemented in deploy.yml). Is that just missing from README, or is there an issue with that? |
|
@LukasWallrich I've opened a new pull request, #622, to work on those changes. Once the pull request is ready, I'll request review from you. |
✅ Spell Check PassedNo spelling issues found in this PR! 🎉 |
✅ Spell Check PassedNo spelling issues found in this PR! 🎉 |
✅ Spell Check PassedNo spelling issues found in this PR! 🎉 |
✅ Spell Check PassedNo spelling issues found in this PR! 🎉 |
Description
@LukasWallrich
This Removes duplicate staging deployment from deploy.yaml (now handled only by staging-aggregate.yaml),
Also adds draft PR filtering to avoid wasted runs, and implements workflow queuing with job timeouts to ensure all open PRs deploy to staging sequentially without blocking each other.
Type of Change
How Has This Been Tested?
Checklist for Developers:
Additional Notes