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

Report

What did you do?

I invoked npx danger local within a Node.js project, specifying a dangerfile.js that lives outside of the project.

Reproduction case:

#!/bin/bash
set -eu

rm -rf ./project ./tool

mkdir tool && (
  cd tool && \
  cat >dangerfile.js <<:DANGERFILE
try{
  console.log(require('array-first'));
  console.log(require('array-last'));
} catch(e) 

According to houndci/hound#1756, Hound CI supports a curated list of Rubocop extensions. However, it is difficult to tell which extensions are available, and which are not.

Please list supported Rubocop extensions on documentation pages.

From @chrisdias:

If I start the auth dance, then press Cancel when asked if I want to let the extension open a URL, the status bar stays at Signing into github.com.... Since I cancelled, I expect it to revert back to Sign in to github.com.

Also (just noticed this) we say into and in to. Not sure which version is right or wrong, or if its based on context :).

Especially in the light of #151 , it would be great if people could just re-generate the whole Id file.

Feature request:

After checking out a change, add an option to a change's right-click menu to trigger Analyze - Inspect Code with a custom scope of all files changed in the gerrit change.

What happened

A common workflow:

1. I make a PR, all the CI goes green, but the overall light is still stuck at yellow
2. I click through to the policy bot UI to see what I need to do to get my thing merged
   
   Unfortun

Error talking to GitHub isn't an actionable error message, we should instead surface the error message that GitHub's API is sending back in case of error.

from src-d/lookout#450 (comment)

Anchors pointing to titles having ., { or } inside, are generated differently by GitBook and GitHub, so when they're used, they don't work in both.

It was assumed GitBook as the preferred way to render our docs, but we should decide if we keep that rule, or if we want to look for a workaround or alternative

exampls

Split from #31

I don't find a checkstyle formatter for brakeman,
https://github.com/presidentbeef/brakeman/blob/master/OPTIONS.md#output-options

So we can use Saddler::Reporter::Github's PullRequestComment.

brakeman -f text \
| saddler report \
  --reporter Saddler::Reporter::Github::PullRequestComment

We want the converter from brakeman output to checkstyle.

(1) The UG mentions that the Sort Groups by and Sort within groups by features have an option to sort by Repo / Branch, which is not true.

(2) The instructions for the Sort within groups by feature use the term "sub-group", which is a little unclear. Instead, we can use the phrase "the entities within the group will be sorted by..."

![image](https://user-images.githubusercontent.com/