Skip to content

This release contains a few bug fixes and from this release, the installation method changed.

Example:

# Specify installation directory ($(go env GOPATH)/bin/) and version.
$ curl -sfL https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh| sh -s -- -b $(go env GOPATH)/bin [vX.Y.Z]

Also, we moved the repository under reviewdog organization and looking for maintainers (#196).
This release contains a few improvement of workflow for org development, like deploy automation of doghouse server.

Assets 7

@haya14busa haya14busa released this Jul 23, 2018 · 219 commits to master since this release

0.9.11 (2018-07-23)

Bug fixes

  • gitlab-mr-discussion: Fix bot could not comment on the merge request created by others #180 (okonomi)

Merged Pull Requests

Assets 18

@haya14busa haya14busa released this Jun 24, 2018 · 262 commits to master since this release

0.9.10 (2018-06-24)

New features: GitLab support! 🎉

reviewdog meets gitlab

gitlab-mr-discussion sample

Added -reporter=gitlab-mr-discussion and -reporter=gitlab-mr-commit options.

$ export REVIEWDOG_GITLAB_API_TOKEN="<token>"
$ export GITLAB_API="https://example.gitlab.com/api/v4"
$ reviewdog -reporter=gitlab-mr-discussion

GitLab CI is also supported.

GitLab CI

Store REVIEWDOG_GITLAB_API_TOKEN in GitLab CI variable.

.gitlab-ci.yml sample

reviwedog:
  script:
    - reviewdog -reporter=gitlab-mr-discussion
    # Or
    - reviewdog -reporter=gitlab-mr-commit

Special thanks

GitLab support (-reporter=gitlab-mr-commit) is implemenbed by @nakatanakatana and @masamotod 👍

Bug Fixes

  • github-pr-review: support pagination to get all posted comments #168 (haya14busa)

Merged Pull Requests:

Assets 18

@haya14busa haya14busa released this Jun 4, 2018 · 362 commits to master since this release

0.9.9 (2018-06-04)

New features:

reviewdog with GitHub Checks feature. https://help.github.com/articles/about-status-checks/#checks

github-pr-check sample
comment in pull-request
commit status

  1. Install reviedog Apps. https://github.com/apps/reviewdog
  2. Set REVIEWDOG_TOKEN or run reviewdog CLI in trusted CI providers.
  • Get token from https://reviewdog.app/gh/{owner}/{repo-name}.
  • $ export REVIEWDOG_TOKEN="xxxxx"
  1. $ reviewdog -conf=.reviewdog.yml -reporter=github-pr-check

Breaking changes:

Deprecate -ci flag #132.
Use -reporter flag instead.
Example:

$ reviewdog -ci=travis
=>
$ reviewdog -reporter=github-pr-review

Merged Pull Requests:

Assets 18

@haya14busa haya14busa released this Aug 10, 2017 · 443 commits to master since this release

0.9.7 (2017-08-09)

GitHub & GitHub Enterprise Support:

As of version 0.9.7, reviewdog completely switched to use new
Pull Reqeust Review Comments API
including GitHub Enterprise. If your GitHub Enterprise version is too low to use
this new API, please use reviewdog version < 0.9.7

Assets 18

@haya14busa haya14busa released this Mar 1, 2017 · 476 commits to master since this release

0.9.6 (2017-03-02)

Support running reviewdog in sub directory for CI
(Supported GitHub & GitHub Enterprise)

e.g.

cd sub/dir && golint . | reviewdog -f=golint -ci=circleci
Assets 18

@haya14busa haya14busa released this Dec 16, 2016 · 524 commits to master since this release

GitHub Review API support https://developer.github.com/changes/2016-12-14-reviews-api/

image

It's experimental because GitHub Preview Pull Request Reviews API itself is in preview period.
reviewdog will also take more advantage of review API later. see #58

0.9.4 (2016-12-16)

Assets 18

@haya14busa haya14busa released this Dec 15, 2016 · 558 commits to master since this release

Introduce (experimental) Project Config Based Run (reviewdog.yml)

Project Configuration Based Run

[experimental]

reviewdog can also be controlled via the reviewdog.yml configuration file instead of "-f" or "-efm" arguments.

With reviewdog.yml, you can run the same commands both CI service and local
environment including editor intergration with ease.

reviewdog.yml

runner:
  <tool-name>:
    cmd: <command> # (required)
    errorformat: # (optional if there is supporeted format for <tool-name>. see reviewdog -list)
      - <list of errorformat>
    name: <tool-name> # (optional. you can overwrite <tool-name> defined by runner key)

  # examples
  golint:
    cmd: golint ./...
    errorformat:
      - "%f:%l:%c: %m"
  govet:
    cmd: go tool vet -all -shadowstrict .
$ reviewdog -diff="git diff master"
project/run_test.go:61:28: [golint] error strings should not end with punctuation
project/run.go:57:18: [errcheck]        defer os.Setenv(name, os.Getenv(name))
project/run.go:58:12: [errcheck]        os.Setenv(name, "")
# You can use -conf to specify config file path.
$ reviewdog -ci=droneio -conf=./reviewdog.yml

Output format for project config based run is one of following formats.

  • <file>: [<tool name>] <message>
  • <file>:<lnum>: [<tool name>] <message>
  • <file>:<lnum>:<col>: [<tool name>] <message>

0.9.3 (2016-12-15)

Assets 17
You can’t perform that action at this time.