π οΈ Troubleshooting β Early-Catch (GitHub Action)
This page focuses on pull requestβbased troubleshooting when using the earlyai/pull-request-test-generation GitHub Action.
For shared issues like memory, token, commit, or coverage errors β see Fundamentals Troubleshooting β.
β No Test Files Generatedβ
This can happen for several different reasons, ranging from configuration or permissions issues to already-covered code.
Please go through the checklist step by step in
π Why No Tests Were Generated
That guide explains every possible cause β including missing CLI installation, coverage command failures, validation errors, SCM permissions, and more β along with how to fix each one.
β οΈ Jest Command failsβ
π Auth Errorsβ
See API Key Missing β
And GitHub Token Issues β
π Permissions Not Setβ
Make sure your workflow includes:
permissions:
contents: write
pull-requests: write
π« Action Doesnβt Triggerβ
Check the event type in your workflow:
on:
pull_request:
types: [opened, reopened, ready_for_review]
π§ͺ No Testable Files in PRβ
TBD
π₯ Memory or Heap Limit Errorsβ
β Commit Push Rejectedβ
See Git Push or Commit Rejected β
π More Helpβ
- Fundamentals Troubleshooting β
- Slack (for invited teams)
- Email us at support@startearly.ai