-
# Report
## What did you do?
I have a gem to hold all danger rules accross multiple projects. I wanted to split up my Dangerfiles into two seperate ones.
One for commit message rules, and one…
-
First I want to thank you guys making this fantastic tool, it works very well and saving a lot time for our team.
And we encounter with some issues recently while working with non-ascii file path.…
-
Hi @wojteklu,
now that Danger supports GitLab I'd be interested in your take on supporting GitLab. I am happy to do the work if you think it can be include in the plugin in a nice way.
-
# Report
## What did you do?
I'm using danger-ruby-swiftlint, using inline_mode which just dispatches the warn/fail messages to danger with the file path. It seems, though, that if the path cont…
-
**Describe the bug**
Our builds have started failing with the following error since using v10.6.2:
```
Error: { HTTPError: Not Found
at fn (/root/.npm/_npx/15/lib/node_modules/danger/node_mod…
-
### Summary
Include a pre-built executable in each release. Use that pre-built artifact in the homebrew tap.
### Why
* Fetching the dependencies and building danger-swift can take a long time, e…
-
Any two files with identical names will make `Danger`/`Shroud` output bogus numbers for the coverage percentage.
It's not too strange on a large project (perhaps with many modules) to have a couple…
-
Hi! Love the idea of Danger and looking forward to trying it out, but my team is using Assembla and I don't see support for it.
I'd love to help in supporting this. What are the requirements in ord…
-
Hi, @hanneskaeufler! Thanks for your awesome plugin.
We are using it inside our review pipeline with great success: https://github.com/wemake-services/kira-review
But, I would like to suggest addi…
-
This code triggers an internal error in `Agda.Termination.TypeBased.Checking.smallerOrEq`:
```agda
{-# OPTIONS --no-syntax-based-termination #-}
{-# OPTIONS --type-based-termination #-}
{-# OPTION…