Skip to main content

Slurp up linter output and send it to a GitHub PR review.

Project description


Build Status codecov

A Continuous Integration CLI that slurps up linter output and sends it to a GitHub PR review.


First, pip install lintly:

$ pip install lintly

Lintly requires Python 2.7 or 3.4+.

Next, set the LINTLY_API_KEY environment variable to your GitHub API Key:

$ export LINTLY_API_KEY="12345"

Finally, pipe the output of your linter to the lintly script:

$ flake8 | lintly

Now you will see a review with linting errors...

Lintly review on a pull request

...and a commit check...

Lintly commit check on a pull request

...on your pull requests! Nifty! 🎉

Supported Git Services

  • GitHub

Support for GitLab and Bitbucket is planned.

Supported Linters

  • flake8

    $ flake8 | lintly --format=flake8
  • black

    $ black --check | lintly --format=black
  • pylint

    • For pylint you must use the json output format.
    $ pylint . --output-format=json | lintly --format=pylint-json
  • eslint

    $ eslint . | lintly --format=eslint
  • stylelint

    $ stylelint . | lintly --format=stylelint
  • cfn-lint

    $ cfn-lint template.yaml | lintly --format=cfn-lint
  • cfn-nag

    $ cfn_nag_scan --input-path cloudformation-template.yaml --output-format=json | lintly --format=cfn-nag

Additional linters can be added by modifying the lintly/ module.


At a minimum Lintly needs to know the following information to determine how to post the correct GitHub PR Review:

  • GitHub API key (--api-key or LINTLY_API_KEY env var)
    • Generate your own API Key here. The API key will need the following GitHub scopes:
      • repo:status so that Lintly can post commit statuses on PRs.
      • public_repo so that Lintly can create pull request reviews on public repos.
      • repo so that Lintly can create pull request reviews on private repos.
  • GitHub repository (--repo or LINTLY_REPO env var)
    • This is your repository in the format grantmcconnaughey/lintly.

    Note: Most Continuous Integration platforms will provide this value automatically.

  • Pull Request number (--pr or LINTLY_PR env var)

    Note: Most Continuous Integration platforms will provide this value automatically.

These configuration values can be provided to Lintly via environment variables or by being passed in as arguments to the Lintly CLI. A list of all configuration values can be viewed by running lintly --help.

Supported Continuous Integration platforms

Lintly works out of the box with all of the CI platforms supported by To add support for new CI platforms create a PR to the repo.

When using these Continuous Integration platforms the repository, pull request number, and commit SHA will be detected automatically.

Travis CI example

To use with Lintly with Travis CI, add the following to your .travis.yml config file:

language: python

    - stage: lint
      install: pip install lintly
      script: flake8 | lintly --format=flake8

  - lint


  • Add support for GitHub Enterprise custom GitHub URLs
  • Configuration to post either a PR comment or PR review
  • Link to Build URL from commit status
  • Support for config file
  • Auto-detect linters
  • GitLab support

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for lintly, version 0.4.3
Filename, size File type Python version Upload date Hashes
Filename, size lintly-0.4.3-py2.py3-none-any.whl (20.2 kB) File type Wheel Python version py2.py3 Upload date Hashes View
Filename, size lintly-0.4.3.tar.gz (365.7 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page