-
Notifications
You must be signed in to change notification settings - Fork 27
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
Combined JSON payloads 2024-W39 #1370
Conversation
… reports) + reformat JSON
@gosuto-inzasheru little confused about why the kill_gauges ended up here twice. I think maybe the gauge report ran and then also the perform_action report. Kinda thing the perform action report is enough and don't need the special kill_gauge handling in the gauge report. Faster to process too. |
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
|
… reports) + reformat JSON
FILENAME:
|
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
|
FILENAME:
|
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
|
… reports) + reformat JSON
final changes to tg message.
FILENAME:
|
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
FILENAME:
|
… reports) + reformat JSON
Automated changes by create-pull-request GitHub action