Conversation
✅ Testkube GitHub IntegrationReview based on commit All tests and quality gates passed.
7 workflows executed
|
|
list_boards, get_board, create_board, update_board, add_board_report, update_board_report, remove_board_report, delete_board and render_board. Board updates are conditional on the version they read and are rebuilt from a fresh read, by ID, after a conflict; render_board queries only the reports the layout shows, each with its own debug state. Boards need a user session: the tools report API tokens with a sign-in hint. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
update_board_report ran NormalizeReport over the report's stored params, so an unrelated edit could fill in creation defaults and change the report's window or segmentation. It now uses ValidateReport, and starts from the kind's defaults only when the kind changes or with replaceParams, as its description says. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
92069ef to
096ca60
Compare
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Name statusDetailsType and statusDetailsReason among the filters, the executions groupBy values and the time-series segments, as the dashboard offers them since kubeshop/testkube-cloud-api#5880. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
list_boards, get_board, create_board, update_board, add_board_report, update_board_report, remove_board_report, delete_board and render_board. Board updates are conditional on the version they read and are rebuilt from a fresh read, by ID, after a conflict; render_board queries only the reports the layout shows, each with its own debug state. Boards need a user session: the tools report API tokens with a sign-in hint.
Pull request description
Checklist (choose whats happened)
Breaking changes
Changes
Fixes