I cannot figure out how to use properly danger on circleci 2.0 with workflows

Support I have a linear workflow where I bundle my app / install libraries (build job) and then run the tests in parallel. (I'm taking Ruby/Rspec as an example).

How can I execute Danger to report test failures on all containers ?

Currently if a job fails on circleCI, the dependent jobs are not ran (ie if I

Colours are replaced by black and white with travis formatter

xcpretty -c Travis output

xcpretty -f `xcpretty-travis-formatter` Travis output
![screen shot 2016-11-22 at 12 19 29 pm](https://cloud.githubusercontent.com/assets/17389431/2052

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description

When running fastlane swift and i

Next step in docs check: not only correction, but also quality.

Some ideas on checks:

• simple "undocumented X" for X in (class, method, constant, parameter, what else?);
• unnecessary documented return value for predicate methods (YARD does it automatically);
• wrongful documented return value type for predicate methods (when it is documented and is not boolean);
• possibly undocumented op

Most of the code should have test coverage already, but it isnt being measured or reported on.

Reports should be uploaded to codecov.io

@juliogonzalez i would like that we document this feature in the advanced section. no need for roman but an example would be good!

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 adding a very useful feature: clickable filenames and lines.
When I review current TODOs I have to go inside the code manually, find the correct line, and then go back again.

<img width="501" alt="Сни

Add tests.

Configure PRs to run rspec tests before allowing merge.