Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.4k
tools: fix lint issue in doctool#11658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Conversation
addaleax commented Mar 2, 2017
Doesn’t the linter catch issues in |
silverwind commented Mar 2, 2017
It does, but I simply forgot to run it after my latest change in that PR. Running |
jasnell left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Let's fast track this to unbreak CI
jasnell commented Mar 2, 2017
PR-URL: #11658 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
jasnell commented Mar 2, 2017
Landed in 172be50 |
silverwind commented Mar 2, 2017
Thanks @jasnell. For the record, the issue happened because my workflow on that PR was basically I'll have to remember to actually run tests on that type of change too, because tests partially cover the doctool |
jasnell commented Mar 2, 2017
It's all good. I just did a lint check on this particular PR. You make want to do a full CI run just to make sure that everything else is still good. |
silverwind commented Mar 2, 2017
|
evanlucas commented Mar 7, 2017
This is not landing cleanly on v7.x-staging. Mind submitting a backport PR? |
silverwind commented Mar 7, 2017
PR-URL: nodejs#11658 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: nodejs#11658 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins commented Apr 17, 2017
do we want to backport to v6.x? |
silverwind commented May 16, 2017
Backport in #13054 |
PR-URL: #11658 Backport-PR-URL: #13054 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: #11658 Backport-PR-URL: #13054 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: nodejs#11658 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: nodejs#11658 Backport-PR-URL: nodejs#13054 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: #11658 Backport-PR-URL: #13054 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: #11658 Backport-PR-URL: #13054 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
Fixes a lint issue introduced in #11167.
cc: @jasnell