Skip to content
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

[lint] Fix no-undef errors #10859

Merged
merged 1 commit into from
Mar 22, 2017
Merged

[lint] Fix no-undef errors #10859

merged 1 commit into from
Mar 22, 2017

Conversation

jbudz
Copy link
Member

@jbudz jbudz commented Mar 22, 2017

This was from #10708, it didn't have the new lint rules.

@spalger spalger merged commit 28021f8 into elastic:master Mar 22, 2017
@stacey-gammon
Copy link
Contributor

Is this okay to backport? I'm getting these errors on 5.x

elastic-jasper added a commit that referenced this pull request Mar 23, 2017
Backports PR #10859

**Commit 1:**
[lint] Fix no-undef errors

* Original sha: 64e8f50
* Authored by Jonathan Budzenski <[email protected]> on 2017-03-22T22:09:12Z
@epixa
Copy link
Contributor

epixa commented Mar 23, 2017

I kicked off a backport of this: #10868

@stacey-gammon Especially if jenkins is failing, feel free to do whatever you think is necessary to get it running successfully again. If for some reason this wasn't OK to backport, it either wouldn't fix the problem (which a backport PR would tell us) or we could revert the backport and figure out why it fixed the problem but was simultaneously not OK to backport :)

@stacey-gammon
Copy link
Contributor

Thanks @epixa, I was very close to backporting myself, but hesitated. Next time I'll charge ahead. :)

epixa pushed a commit that referenced this pull request Mar 23, 2017
Backports PR #10859

**Commit 1:**
[lint] Fix no-undef errors

* Original sha: 64e8f50
* Authored by Jonathan Budzenski <[email protected]> on 2017-03-22T22:09:12Z
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants