Skip to main content

πŸ› οΈ 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​

See Jest Setup Missing β†’


πŸ” Auth Errors​

See API Key Missing β†’
And GitHub Token Issues β†’


πŸ”’ Permissions Not Set​

Make sure your workflow includes:

permissions:
contents: write
pull-requests: write

See Permissions Fixes β†’


🚫 Action Doesn’t Trigger​

Check the event type in your workflow:

on:
pull_request:
types: [opened, reopened, ready_for_review]

See Event Type Guidance β†’


πŸ§ͺ No Testable Files in PR​

TBD


πŸ’₯ Memory or Heap Limit Errors​

See Out of Memory Fixes β†’


❌ Commit Push Rejected​

See Git Push or Commit Rejected β†’


πŸ“š More Help​