We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is an idea proposed by @bronzdoc:
What if we have 12 shitlist.json files because the CI service is running 12 different containers? It would be great if we can have a sort of "merge" feature that merges shitlist.json files by root cause
What if we have 12 shitlist.json files because the CI service is running 12 different containers?
It would be great if we can have a sort of "merge" feature that merges shitlist.json files by root cause
It would be great to group by root cause and then list all unique occurrences.
The text was updated successfully, but these errors were encountered:
@arielj What we were discussing.
So just to inform, I made a CLI app that merges them. It could be easily translated into ruby for next_rails.
As for the second part, currently running some tests on some rspec json output I have
Sorry, something went wrong.
I translated, somewhat, what I did in elixir to ruby and added it in the PR above. Hope it helps.
bronzdoc
Successfully merging a pull request may close this issue.
This is an idea proposed by @bronzdoc:
It would be great to group by root cause and then list all unique occurrences.
The text was updated successfully, but these errors were encountered: