-
-
Notifications
You must be signed in to change notification settings - Fork 131
Update troubleshooting section for disk space issues #524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Set build step id to `buildStep` to help readers avoid confusion.
Clarified disk space issues when running multiple jobs sequentially in GitHub Actions workflows. Updated recommendations for using GitHub-hosted larger runners and self-hosted/cloud runners.
WalkthroughDocumentation for troubleshooting GitHub Actions disk-space issues was expanded: added explicit rationale about limited GitHub-hosted runner disk space and large Unity images, described disk-space risks when jobs run sequentially, introduced a new “GitHub-Hosted Larger Runners” remediation, and expanded the self-hosted/cloud runners guidance with examples. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/09-troubleshooting/common-issues.mdx(2 hunks)
🧰 Additional context used
🪛 GitHub Actions: 👩💻
docs/09-troubleshooting/common-issues.mdx
[error] 1-1: Prettier formatting check failed for docs/09-troubleshooting/common-issues.mdx. Run 'prettier --write' to fix code style issues.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: build_and_preview
🔇 Additional comments (1)
docs/09-troubleshooting/common-issues.mdx (1)
282-292: Links verified and accessible.Both external documentation references are accessible:
- GitHub-Hosted Larger Runners documentation returns HTTP 200 (direct access)
- game.ci Cloud Runners documentation returns HTTP 301 (permanent redirect, properly handled by browsers/clients)
The content is well-structured, actionable, and correctly references current external documentation. No issues identified.
|
Visit the preview URL for this PR (updated for commit d3b2e64): https://game-ci-5559f--pr524-davidmfinol-patch-4-9o1bv1mv.web.app (expires Sat, 29 Nov 2025 18:04:57 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 1f0574f15f83e11bfc148eae8646486a6d0e078b |
…mentation into davidmfinol-patch-4

Changes
Checklist
code of conduct
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.