Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
8 changes: 4 additions & 4 deletions generated_types.json
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."

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 the generic formatting-prompt description

For SDK users inspecting Slack actions on logs, environment_update, topic_digest, or generic windowed automations, this field is now documented with a Patterns-run output prompt even though those triggers do not necessarily have selected Patterns or pattern outcomes. The webhook sibling still describes the field generically, so the platform schema should explain that this value contains formatting instructions—or document the default separately—rather than embedding a Patterns-specific prompt across every Slack action before regenerating these types.

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 @@ -9880,7 +9880,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
44 changes: 40 additions & 4 deletions py/src/braintrust/_generated_types.py
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 @@ -3100,7 +3127,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
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 57e68e3bee66f80f) -- do not modify"""

from ._generated_types import (
Acl,
Expand Down