Skip to main content

🛠️ Troubleshooting — Early CLI (early generate-pr)

This guide focuses on issues specific to the Early CLI when running in Jenkins, CircleCI, or other CI/CD environments.

For shared topics like memory crashes, token auth, Jest setup, or commit issues — 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.

📦 CLI Installation Fails (401 or npm auth error)​

Likely due to GitHub Packages authentication failure.

See GitHub Packages Install Failures →

🔑 Missing or Invalid API Key​

See API Key Missing or Invalid →

🔐 GitHub Token Error or Git Push Fails​

See Token Insufficient or Git Push Fails →

💥 Out of Memory Error​

See Node.js Heap / OOM Fixes →

🚫 No Test Files Generated​

See Testable Code Not Found →

⚠️ Jest Not Installed or Misconfigured​

See Jest Setup Missing →

⚠️ Lint / Prettier Hook Breaks Commit​

If commits fail due to linting or formatting rules in your repo, configure:

export LINT_COMMAND="npx --no eslint $early_filename --fix"
export PRETTIER_COMMAND="npx --no prettier $early_filename --write"

See Lint/Prettier Failures →

🧪 Coverage Command Fails​

See Custom Coverage Command Errors →

⚙️ SCM or Git Errors in CI​

Ensure:

  • Git is installed and configured in the agent image
  • Token is injected as a credential
  • You are using a full clone (not shallow)

See Git or SCM Errors →

📚 More Help​