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

The GitHub Integration just fails with a GitHub Error Response if your Issue Comment gets too long.

It’d be great if we truncated the message, & added a [truncated] 📝?

Thoughts @orta ? I’m happy to implement this if you have advice!

reviewdog/reviewdog#405 introduced the -tee option, but there is no mention of the feature in the readme. This would be helpful info for us who are trying to implement/debug this tool

With a .stylelintrc.json file with:

{
  "extends": [
    "stylelint-config-sass-guidelines",
    "stylelint-config-prettier"
  ],
  ...
}

I get this error:

Error: Could not find "stylelint-config-sass-guidelines". Do you need a `configBasedir`?
    at module.exports (/home/linters/app/node_modules/stylelint/lib/utils/configurationError.js:8:28)
    at getModulePat

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.

IntelliJ version: 2018.3.2
Gerrit version: 1.1.1-146

If one adds a topic label in the push dialog and the laben contains whitespaces (i.e. "change ABC") the autofill of the push target is not working anylonger.

Steps to reproduce:

• open push dialog
• type two words in the "Topic" text field (i.e. "change ABC")
• click on checkbox "push to gerrit"
• click on checkbox "push to gerrit" t

It might be useful to highlight tab characters (if only for Makefiles).

Also git allows to highlight trailing whitespaces, which is lost in diffr (because we trim all color codes).

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

It would be nice if diff-goto-source (C-c C-c) worked when this is invoked from github-review-forge-pr-at-point. All it needs to do is set the current directory to the git working tree in the diff-mode buffer. In many cases it does not matter too much whether the user has the "correct" branch is checked out - it just needs to be close.

Caused by src-d/lookout#447 (comment)

It is needed to decide how to create PNG versions of SVG to be used in docs (because GitBook does not support SVG).

Currently it is done with a screenshot from mermaid view, but it does not scale and can not be integrated in the CI.

Currently it's assumed everything is in English.
This can lead to false positives (especially in French and Spanish).
It should be checked which language the document is written in
and typos should be fixed accordingly.

Split from #31

rails_best_practices has format option, so we can set a checkstyle formatter.
I find a checkstyle formatter for rails_best_practices.

https://github.com/maroekun/rails_best_practices-formatter

I'm not sure this works fine with saddler. 😓

What problem(s) did you run into that caused you to request additional documentation? What, if any, existing documentation relates to this proposal?

Currently