-
Notifications
You must be signed in to change notification settings - Fork 18
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
keep using default ignore list #96
Conversation
Signed-off-by: Dirk Thomas <dirk-thomas@users.noreply.github.com>
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.
Have you run CI yet?
I'll approve it in the interest of getting CI green again, though I don't understand the change. I assume you reproduced it locally and it actually fixes the issue.
No, due to the nature of the change I don't think it makes sense to run CI builds on Jenkins for this.
Yes. |
To see if it fixes the linter error it purports to fix? I'm ok with going without CI I guess, but it only needs to go up to |
Signed-off-by: Dirk Thomas <dirk-thomas@users.noreply.github.com> (cherry picked from commit 570df24)
Signed-off-by: Dirk Thomas <dirk-thomas@users.noreply.github.com> (cherry picked from commit 570df24)
Signed-off-by: Dirk Thomas <dirk-thomas@users.noreply.github.com> (cherry picked from commit 570df24)
Follow up of #89. Fixes linter warning.