pages build and deployment action no longer being run by GitHub Pages after push to main branch causing a 404?

[Dominique8D]

Select Topic Area

Question

Body

As of sometime yesterday GitHub Pages no longer seems to trigger after a push has been done to the main branch:

I haven't worked on the website for a while but as of trying to continue working today, I had to update my deploy file to be able to continue due to an error on an outdated action within it's file.
After updating the file the GitHub Pages action only worked one more time and afterwards it no longer seems to trigger.

At the same time my Website no longer works displaying a standard GitHub Pages 404 Message:

This occurs even if I manually deploy from a branch that is using a commit where previously it was working. (Using the Pages settings)
This leads me to believe that the issue may be a bug and not my setup since the commit definitely worked a few months back.
Though if this is not the case and my project setup is the cause please let me know:
Pages website: https://dominique8d.github.io/project-react/
Repo: https://github.com/Dominique8D/project-react

[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. ⭐

[Dominique8D]

In the end I solved it myself like so:

• Go to GitHub Pages settings
• Under Build and deployment set branch to gh-pages
• Using terminal of repo:
  • On my master/main branch build my project using: npm run build
  • Push dist to gh-pages branch using: npx gh-pages -d dist
• Afterwards the page is visible again

What I think happened is that this part happened automatically previously but as some update I need to do this manually.

[Dominique8D]

Note that you will also need to create the gh-pages branch yourself: git branch gh-pages.
The commands only will create a new commit (and by extension a release) if there are actual changes in the build (actual website changes).