Skip to content

Conversation

@krisds
Copy link
Contributor

@krisds krisds commented Jan 30, 2019

Hi. I'm an LGTM developer, and had some time to fix a few alerts flagged in Elasticsearch by our analyses.

There should be one commit per file, and the commit messages have links back to the original alerts to make it easy for you to check what each thing is about.

Let me know if this is helpful or not, what I can do better, or if there are any specific (types of) alerts you're interested in which I can look at in the future.

Kris De Schutter added 6 commits January 30, 2019 12:03
@ghost
Copy link

ghost commented Jan 30, 2019

Hi @krisds, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

@krisds
Copy link
Contributor Author

krisds commented Jan 30, 2019

My github profile should now list my secondary email. Sorry about that oversight.

@colings86
Copy link
Contributor

@krisds Would you mind splitting these changes into multiple PRs, one for each file you have changed? That way we can assess the changes in different areas of the code separately which will make it easier to review and get any accepted changes merged.

With these kinds of changes its often difficult to review as one PR as for each change there may be subtle impacts on functionality that we need to consider (not saying they are not bugs, just that we have to consider if the change will impact something else in that area). Splitting the changes into separate PRs makes it easier for different people who are familiar with different parts of the codebase to review and merge each change separately

Thanks

@krisds
Copy link
Contributor Author

krisds commented Jan 31, 2019

No problem. I will do that.

@colings86
Copy link
Contributor

I'm going to close this since we are tracking these fixes in the newly opened separate PRs. Thanks for separating the PRs @krisds

@colings86 colings86 closed this Feb 5, 2019
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.

2 participants