[Roonil03]

Bug Description

Expected: Daily and code-push rating refreshes publish the site without a Pages deployment error.

Actual: GitHub's branch-based Pages run for the bot commit failed with HTTP 400 because another Pages deployment from the refresh workflow was still in progress. The punycode deprecation warning was incidental.

Root Cause

The repository publishes main / through GitHub Pages while the refresh workflow also deploys a Pages artifact. The workflow pushed the generated ratings/site commit before its own artifact deployment completed. That push started GitHub's branch-based publisher, and the two deployment requests overlapped. The observed failure was for c943eb4 while the deployment associated with 9917611 was active.

Fix Description

On code pushes, let the existing branch-based Pages publisher deploy the committed root site and skip the custom artifact deployment. On scheduled and manual refreshes, deploy and verify the built artifact first, then push the generated ratings and root-site commit as github-actions[bot]. This sequences the two publishers instead of allowing them to race.

How to Reproduce (Before Fix)

1. Run the scheduled refresh with the repository's branch-based Pages publishing enabled.
2. Let the workflow commit refreshed ratings and root assets before its artifact deployment step.
3. Observe the branch-based Pages run fail to create its deployment while the other Pages deployment is active.

How to Verify (After Fix)

1. Merge this PR and manually dispatch the refresh workflow on main.
2. Confirm the artifact deployment and live-site verification complete before the bot commit is pushed.
3. Confirm the resulting branch-based Pages run has no HTTP 400 overlap; on a code push, confirm the custom Pages steps are skipped.

Impact Assessment

• Severity: Medium
• Users affected: All users waiting for a ratings update during a deployment collision
• Duration: The competing publication paths were active after root-based Pages publishing was introduced; the reported collision occurred on 2026-11-03.

Regression Risk

A failed bot push after successful artifact deployment could leave the live site ahead of the repository until the next refresh. The workflow reports that push failure. Code-push publishing continues to depend on the repository's configured main / Pages source.

Checklist

• Root cause identified and documented above
• Fix addresses the root cause (not just symptoms)
• Added test to prevent regression
• Existing tests pass locally
• Tested the specific reproduction steps

Related Issues

• Failed Pages run: https://github.com/iecseadmin/CompTeamDemo/actions/runs/41609588528