GitHub Pages publication repeatedly stalls in syncing_files

[daedongyeosu]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Repository: https://github.com/daedongyeosu/daedong-yeosu-foodmap
Public site: https://daedongmap.com/
Publishing source: main / root (legacy branch publishing)
Target commit: 054ac82c90e6af7069d071f1521d92e78b0bbf05

A reviewed and validated bug fix is merged, but the public site still serves the previous version.
Build and artifact upload succeed. The Pages deployment stalls in syncing_files and times out after ten minutes.
Initial run: https://github.com/daedongyeosu/daedong-yeosu-foodmap/actions/runs/42829540252
Fresh rebuild: https://github.com/daedongyeosu/daedong-yeosu-foodmap/actions/runs/42831610336
Third failed build: https://github.com/daedongyeosu/daedong-yeosu-foodmap/actions/runs/42835223235
Last successful run: https://github.com/daedongyeosu/daedong-yeosu-foodmap/actions/runs/42820310072

The artifact is approximately 733 MB, almost the same size as the preceding successful build. Earlier deployment environment records are marked failure, not in progress. No Pages source, custom domain, or permission settings have been changed. The preview deployment of this fix succeeded and has been tested.

Could you investigate the Pages file synchronization state for this repository and advise how to restore publication while preserving the working site and domain?

No credentials or private customer records are included.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[daedongyeosu]

Update: a fresh release has now been validated through new commits. The preview repository published successfully: https://github.com/daedongyeosu/daedong-yeosu-foodmap-preview/actions/runs/42842859406 (commit 8478e92226364504057264af639112c60642c781), and the live preview version was verified.

The production repository still timed out in syncing_files on a different, newly merged commit: https://github.com/daedongyeosu/daedong-yeosu-foodmap/actions/runs/42843976926 (commit 6bb12827e72ce25d8adc0eb32af4e7d6168ab8be). Its required CI and CodeQL checks passed. A fresh official rebuild of that commit is currently running: https://github.com/daedongyeosu/daedong-yeosu-foodmap/actions/runs/42845969036 .

Both sites use branch publishing from main / root with HTTPS enforced. The Pages source, domain settings and permissions have not been changed. Could GitHub investigate whether file synchronization for the production Pages site is stuck? The production domain continues to serve the preceding version.