Guy Kisel

It's really just a nice-to-have thing, it doesn't strike me as being urgently needed. Cloning the repo isn't that bad :)

nah just generally related to installing python dependencies before running python linters. people often have requirements files nested in subfolders.

``` Traceback (most recent call last): File "/home/travis/virtualenv/python3.6.3/bin/inline-plz", line 11, in load_entry_point('inlineplz', 'console_scripts', 'inline-plz')() File "/home/travis/build/guykisel/inline-plz/inlineplz/main.py", line 61, in main result = inline(args) File "/home/travis/build/guykisel/inline-plz/inlineplz/main.py", line 148, in inline my_interface...

the readme still references token: ``` You'll also need to provide the following either in the command line or via environment variables: owner: the repo organization/owner repo: the repo name...

looking at the console logs from the last run, although it passed, it doesnt look like it tried to run the github interface: ```Installation and running of stylint took 7...

so i think something might be wrong with the github integration

for testing purposes in the PR i think it's okay to have it depend directly on the git repo. for merging i'd be okay with depending on the git repo...

https://github.com/guykisel/inline-plz/pull/193

Might need to convert markdownlint to run per file instead of letting it choose what files to run on so that it doesn't dive deep into node_modules.

Hey @xyngfei , can you give me some more information? What steps did you follow to install your dependencies? What is the output of `pip list`?