Deployment to github pages fails due to Space issue getting error System.IO.IOException: No space left on device

[rahulshrivastava-eaton]

Select Topic Area

Bug

Body

I am deploying a static site (selenium allure based reports) from gh-pages branch, over the time size of the branch might have increased very large due to historical data and now it is ~15GB space . I am getting this error in automatic deployment .
Error : System.IO.IOException: No space left on device : '/home/runner/runners/2.320.0/_diag/Worker_20241016-045229-utc.log' at System.IO.RandomAccess.WriteAtOffset

FYI : My workflow which is in another repository is doing the deploying on other remote repo via gh-pages branch.

I am not able to understand few things here -

1. when i do automatic deployment via action peaceiris/actions-gh-pages@v4 , which runner is getting used here for doing the deployment , I am asking this because even after using the large runner for my main workflow i am getting same error ?
2. where does gh-pages site use to get hosted , when it publish the site from 'gh-pages' site ?
3. i can't see any actions in the remote repo , so from where 'pages build and deployment' is getting executed and can i change it to use specific large runner to resolve my issue ?

`name: Smoke
run-name: smoke
on:
workflow_dispatch:
schedule:
- cron: '30 3,15 * * *'
push:
branches:

• release/x.x
  permissions: write-all

jobs:
Job_Generate_Allure_Reorts:
if: ${{ !cancelled() }}
needs: [job_smoke_run]
runs-on: ubuntu-latest-4-cores
name: Publish Allure Results
steps:
- name: Checkout gh-pages to Get Allure history
uses: actions/checkout@v4
if: ${{ !cancelled() }}
continue-on-error: true
with:
repository:
token:
ref: gh-pages
path: gh-pages
- name : Step - download allure test reports
uses: actions/download-artifact@v4
if: ${{ !cancelled() }}
with:
name:
path:
- name: Deploy report to remote repo in Github Pages
if: ${{ !cancelled() }}
uses: peaceiris/actions-gh-pages@v4
with:
publish_dir: allure-history
external_repository:
publish_branch: gh-pages
personal_token: `

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