Skip to content

Conversation

@Oliver-Sellwood
Copy link

#3161 - no, ci error
#3141 - no, ci error
#3017 - no, breaks tests
#2881 - bad object
#2858 - yes
#2759 (this one actually happened to me) - yes
#2750 - no, undocumented
#2653 - bad object
jertel/elastalert2#157 - yes

tests are breaking in master anyway so I couldn't test locally if the pr's with CI errors actually break tests.

Would it be a good idea to push changes from this fork to https://github.com/jertel/elastalert2 and let them handle maintenance?

@Oliver-Sellwood
Copy link
Author

@synhershko

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants