Skip to content

chore: Update platform types - #715

Open
braintrust-bot[bot] wants to merge 1 commit into
mainfrom
chore/regenerate-sdk-python-types
Open

chore: Update platform types#715
braintrust-bot[bot] wants to merge 1 commit into
mainfrom
chore/regenerate-sdk-python-types

Conversation

@braintrust-bot

Copy link
Copy Markdown
Contributor

Automated regeneration of SDK types.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 34fb7d588b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "Codex (@codex) review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".

Comment on lines +1694 to +1696
Publish a Slack mrkdwn digest.

Include a complete "*Pattern outcomes*" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore a generic formatting-prompt description

For ProjectAutomationConfig with event_type='logs', this field accepts arbitrary Loop formatting instructions and has no schema default, but its generated documentation now prescribes a Pattern run-report digest whose inputs do not exist for general log automations. The same shared text is also propagated to environment_update and generic windowed Slack actions, so SDK users inspecting these public types receive configuration guidance specific to an unrelated workflow; keep the field description generic and place this digest prompt in the Pattern-specific implementation/default instead.

Useful? React with 👍 / 👎.

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.

0 participants