Skip to content

tools: update ESLint to 5.14.0 - #26142

Merged
cjihrig merged 1 commit into
nodejs:masterfrom
cjihrig:eslint
Feb 18, 2019
Merged

tools: update ESLint to 5.14.0#26142
cjihrig merged 1 commit into
nodejs:masterfrom
cjihrig:eslint

Conversation

@cjihrig

Copy link
Copy Markdown
Contributor

Update ESLint to 5.14.0

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-botnodejs-github-bot added the tools Issues and PRs related to the tools directory. label Feb 15, 2019

@TrottTrott left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rubber-stamp LGTM

@TrottTrott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Feb 15, 2019
Update ESLint to 5.14.0
PR-URL: nodejs#26142
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Wyatt Preul <wpreul@gmail.com>
@cjihrig

Copy link
Copy Markdown
ContributorAuthor

@cjihrig
cjihrig merged commit 77b39c2 into nodejs:masterFeb 18, 2019
@cjihrig
cjihrig deleted the eslint branch February 18, 2019 02:58
addaleax pushed a commit that referenced this pull request Feb 18, 2019
Update ESLint to 5.14.0
PR-URL: #26142
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Wyatt Preul <wpreul@gmail.com>
@BridgeARBridgeAR mentioned this pull request Feb 26, 2019
rvagg pushed a commit that referenced this pull request Feb 28, 2019
Update ESLint to 5.14.0
PR-URL: #26142
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Wyatt Preul <wpreul@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.toolsIssues and PRs related to the tools directory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@cjihrig@nodejs-github-bot@geek@Trott