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.

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).

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.

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

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

Currently