Skip to content

chore: Update platform types #727

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.

Sign up for GitHub

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

Closed
braintrust-bot wants to merge 1 commit into from
Closed

chore: Update platform types #727

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions generated_types.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5651,7 +5651,7 @@
"type": "string",
"minLength": 1,
"maxLength": 10000,
"description": "Instructions for Loop to format content sent to this destination"
"description": "Publish a Slack mrkdwn digest.\n\nInclude 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.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report."

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 1, 2026

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 Scope the Pattern prompt to Pattern automations

This branch describes the Slack action for a generic ProjectAutomationConfig with event_type: "logs", but the new description requires a run report and selected Patterns, concepts that are not available for arbitrary log automations. The same specialized text was also propagated to environment_update and topic_digest, so SDK documentation and any tooling that consumes these schema descriptions will direct users to supply inapplicable formatting instructions; retain the generic description for those variants and scope this Pattern-specific prompt to the appropriate automation.

Useful? React with 👍 / 👎.

}
},
"required": [
Expand Down Expand Up @@ -5996,7 +5996,7 @@
"type": "string",
"minLength": 1,
"maxLength": 10000,
"description": "Instructions for Loop to format content sent to this destination"
"description": "Publish a Slack mrkdwn digest.\n\nInclude 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.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report."
}
},
"required": [
Expand Down Expand Up @@ -8676,7 +8676,7 @@
"type": "string",
"minLength": 1,
"maxLength": 10000,
"description": "Instructions for Loop to format content sent to this destination"
"description": "Publish a Slack mrkdwn digest.\n\nInclude 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.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report."
}
},
"required": [
Expand Down Expand Up @@ -9805,6 +9805,10 @@
"type": "string",
"minLength": 1
},
"endpoint_name": {
"type": "string",
"minLength": 1
},
"reasoning_effort": {
"type": "string",
"enum": [
Expand Down Expand Up @@ -9880,7 +9884,7 @@
"type": "string",
"minLength": 1,
"maxLength": 10000,
"description": "Instructions for Loop to format content sent to this destination"
"description": "Publish a Slack mrkdwn digest.\n\nInclude 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.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report."
}
},
"required": [
Expand Down
45 changes: 41 additions & 4 deletions py/src/braintrust/_generated_types.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1691,7 +1691,16 @@ class ProjectAutomationConfigAction1(TypedDict):
"""
formatting_prompt: NotRequired[str | None]
"""
Instructions for Loop to format content sent to this destination
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.

Use this row format exactly:
• <pattern_url|Pattern title> — `outcome`

If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say "No pattern outcomes."

After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report.
"""


Expand Down Expand Up @@ -1817,7 +1826,16 @@ class ProjectAutomationConfig4Action1(TypedDict):
"""
formatting_prompt: NotRequired[str | None]
"""
Instructions for Loop to format content sent to this destination
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.

Use this row format exactly:
• <pattern_url|Pattern title> — `outcome`

If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say "No pattern outcomes."

After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report.
"""


Expand Down Expand Up @@ -2663,7 +2681,16 @@ class TopicDigestAutomationConfigAction(TypedDict):
"""
formatting_prompt: NotRequired[str | None]
"""
Instructions for Loop to format content sent to this destination
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.

Use this row format exactly:
• <pattern_url|Pattern title> — `outcome`

If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say "No pattern outcomes."

After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report.
"""


Expand Down Expand Up @@ -3061,6 +3088,7 @@ class WindowedAutomationConfigLoop(TypedDict):
"""
harness: NotRequired[Literal['native', 'codex', 'claude-code'] | None]
model: NotRequired[str | None]
endpoint_name: NotRequired[str | None]
reasoning_effort: NotRequired[
Literal['none', 'minimal', 'low', 'medium', 'high', 'xhigh', 'max']
]
Expand Down Expand Up @@ -3100,7 +3128,16 @@ class WindowedAutomationConfigActions1(TypedDict):
"""
formatting_prompt: NotRequired[str | None]
"""
Instructions for Loop to format content sent to this destination
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.

Use this row format exactly:
• <pattern_url|Pattern title> — `outcome`

If a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say "No pattern outcomes."

After the outcome list, include a "*Highlights*" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report.
"""


Expand Down
2 changes: 1 addition & 1 deletion py/src/braintrust/generated_types.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
"""Auto-generated file (content hash 9963a3f7375263a4) -- do not modify"""
"""Auto-generated file (content hash a987538bfc6c9ff3) -- do not modify"""

from ._generated_types import (
Acl,
Expand Down