danger-js icon indicating copy to clipboard operation
danger-js copied to clipboard

⚠️ Stop saying "you forgot to …" in code review

Results 143 danger-js issues
Sort by recently updated
recently updated
newest added

* resolves #1274 * refactors `Dockerfile` to optimize for size - converts to use a two stage build with only the minimum in the final stage - applies `yarn-audit-fix` during...

I've got a file within my repo which has had a parent folder renamed (e.g. from `/tests/seach/index.spec.js` to `/tests/search/index.spec.js`) I'm running some tests on the diff of modified files, and...

Where is all the clear explanations of all the cli usage?

You Can Do This
documentation

**Describe the bug** Sometimes you want that people resolve the danger comment. Example on a fail message. I would like a new command-line option that forces to create a thread...

enhancement
Open for Discussion
[platform] GitLab

**Describe the bug** https://danger.systems/js/guides/the_dangerfile.html#using-danger-and-faking-being-on-a-ci Following the instruction fails due to base branch is main and no way to change that with a flag since `ci` has no `-b` flag. **To...

enhancement
You Can Do This

**Describe the bug** When using the built-in native TypeScript transpiler, the `extends` field is not supported and only the explicit `compilerOptions` are used. This field is sometimes used in monorepos...

bug
enhancement
help wanted
You Can Do This

danger-js binaries installed via Homebrew are built in x86_64 architecture. It causes https://github.com/danger/swift/issues/464. We need arm64 binary for M1 macs.

enhancement

Follow up based on discussion in: https://github.com/danger/danger-js/pull/1006#discussion_r392591146 This PR now only contains the changes needed to support Azure Devops.

I want to get the value of `danger ci --id` to use in rules. The intent is to run danger twice on CI pipeline, first time early to report coding...

feature

Replaces https://github.com/danger/danger-js/pull/1254 Noticed that "danger:prepush" ran commands with ";" rather "&&" meaning the next command is still executed if the previous one failed. This resulted in very weird errors due...