While inspecting the installer, I noticed the fallbacks for Linux / OSX when appdirs isn't available (in data_dir()).

Wouldn't it make sense to add an if for Windows based on %APPDATA% or %LOCALAPPDATA%, before resorting to globally installing appdirs?

Right now dot command is required for scabbard to be useful. We could build a validation step in Gradle plugin that checks for availability of dot and fails the build. Additionally providing commands to install dot in messages would be nice.

The notice-pre-processor.kts file allows for customisation of the generated notice file, see https://github.com/oss-review-toolkit/ort/blob/master/docs/notice-pre-processor-kts.md.

Not all customisations seem possible, though. I would like to:

• customize the notice separator
• get rid of the separator between the different headers
• include the license name/id before the license text

Hello!

SASS has partials, which filenames start with _, but it's not written in @import: https://sass-lang.com/documentation/at-rules/import

So, we're having incorrect links (with 404).

Example: https://github.com/nana-4/materia-theme/blob/8988c72/src/chrome/chrome-scrollbar-dark/scrollbars.scss

Incorrect link to https://github.com/nana-4/materia-theme/blob/8988c72/src/_sass/colors

Running these commands

git clone https://github.com/paramiko/paramiko.git
cd paramiko
git checkout -b my2.2.3 2.2.3
git tag to-backport 56c96a65
git deps -r -e my2.2.3

I get

Fatal: -L invalid line number: 0
Traceback (most recent call last):
  File "/usr/bin/git-deps", line 10, in <module>
    sys.exit(run())
  File "/usr/lib/python3.6/site-packages/git_deps/cli.py

The documentation stands "Webpack 1.x/2.x plugin" does it means that version 3 is not supported?
Is there plans to support 3 version?

If an undefined function has a standard name (like printf), should we check also the prototype to increase the confidence that we really may assume that the function behaves like the standard function?

Awesome project!

Any chance you'd consider modifying the project so branches other than master could be specified? Or would you be open to accepting pull-requests that do that?

Given a simple DockerMake.yml:

foobar:
    FROM: ubuntu:xenial

we can build prepend a Docker registry URL like this:

$ docker-make -r quay.io/elvis foobar
...
  docker-make built: quay.io/elvis/foobar

docker-make finished.
Built: 
 * quay.io/elvis/foobar

However, if the registry is running on a non-standard port it causes problems:

$ docker-make -r q

If you run ?pkgnet::InheritanceReport, you'll see a section like this:

And the same on the pkgdown site (https://uptake.github.io/pkgnet/reference/InheritanceReporter.html)

![image](https://user-images.githubusercontent.com/7608904/80892622-17765900-8c91-11ea-9292-46818c0037db

Following the README.md "Run:" instructions I get the following:

[user@fedajh ansible-viz]$ gem install bundle
Fetching: bundle-0.0.1.gem (100%)
Successfully installed bundle-0.0.1
Parsing documentation for bundle-0.0.1
Installing ri documentation for bundle-0.0.1
Done installing documentation for bundle after 0 seconds
1 gem installed
[user@fedajh ansible-viz]$ bundle install
Trac