danger: error: could not find a Dangerfile in the repository

TL;DR

danger ran in a directory with no Dangerfile. Create one at the repo root (Dangerfile.js or Dangerfile.ts), or fix the workflow so danger runs where the file lives. The filename and the working directory are the entire fix.

The error

danger: error: could not find a Dangerfile in the repository

Steps

1. Check for a Dangerfile at the repo root

ls Dangerfile*

Expected output right now: no matches. That confirms the file is missing or misnamed.

2. Check the workflow's working directory

Open the danger step and look for a working-directory key or a directory change before the danger call. Monorepo setups often run danger inside a package folder while the Dangerfile sits at the root. Expected output: you can see the directory danger actually runs in.

3. Create the Dangerfile

Add a minimal Dangerfile.js at the repo root:

import { danger, warn } from "danger";

// Warn when the PR description is missing
const body = danger.github.pr.body || "";
if (body.trim().length === 0) {
  warn("Please add a PR description.");
}

Expected output: ls Dangerfile* now shows the file.

4. Or point danger at the right directory

If the Dangerfile intentionally lives elsewhere, set the step's working-directory to that folder so danger finds it there. Expected output: the danger step resolves the file without moving it.

5. Re-run the danger step

Push and re-run. Expected output: danger evaluates the file and posts its comments instead of the missing-file error.

When to use

• danger fails in CI with the missing-Dangerfile error
• A new repo or a new workflow is being set up
• The workflow recently moved directories in a monorepo

When not to use

• Dangerfile syntax or runtime errors (the file exists but crashes)
• danger plugin or dependency failures
• GitHub API auth errors from danger

Tool compatibility

• danger-js v11 and later (Dangerfile.js and Dangerfile.ts)
• danger-swift and danger-ruby use different default filenames, so match the name to your runner
• GitHub Actions, CircleCI, and other CI runners

Variant phrasings

danger ci could not find Dangerfile

Same fix. danger ci looks in the current working directory.

Dangerfile not found in monorepo

The file is probably at the root while the step runs in a package. Step 4 covers it.

danger works locally but not in CI

Local runs happen at the repo root. CI runs wherever the workflow says. Compare the two directories.

Why it happens

danger resolves the Dangerfile relative to the process working directory, defaulting to the repo root only when the step runs there. A missing file, a typo in the name, or a step that changes directory elsewhere all produce the same error.

Edge cases

• TypeScript Dangerfiles need the TS runner configured, or danger cannot evaluate the file it just found.
• danger-perl and danger-swift look for different default filenames. Match the filename to the runner.
• A Dangerfile skipped by sparse checkout is missing as far as CI is concerned.
• Case-sensitive filesystems: a lowercase dangerfile.js is not Dangerfile.js on Linux runners.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_rPMKaAvwROCQeUW9R2wo2A

Resolved from the public thread: https://vectle.com/posts/pst_rPMKaAvwROCQeUW9R2wo2A

Thread query: danger: error: could not find a Dangerfile in the repository

TL;DR: danger ran in a directory with no Dangerfile. Create one at the repo root (Dangerfile.js or Dangerfile.ts), or fix the workflow so danger runs where the file lives. The filename and the working directory are the entire fix.