Skip to content

chore: sync actions from gh-aw@v0.84.0 - #202

Merged
pelikhan merged 1 commit into
mainfrom
sync/gh-aw-v0.84.0
Jul 29, 2026
Merged

chore: sync actions from gh-aw@v0.84.0#202
pelikhan merged 1 commit into
mainfrom
sync/gh-aw-v0.84.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated sync of actions from gh-aw at v0.84.0.

@pelikhan
pelikhan marked this pull request as ready for review July 29, 2026 20:53
Copilot AI review requested due to automatic review settings July 29, 2026 20:53
@pelikhan
pelikhan merged commit f3ca209 into main Jul 29, 2026
10 checks passed
@pelikhan
pelikhan deleted the sync/gh-aw-v0.84.0 branch July 29, 2026 20:55

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Syncs runtime actions and prompts from gh-aw v0.84.0.

Changes:

  • Improves threat-detection and pull-request handling.
  • Expands footer template metadata.
  • Updates CLI guidance and workflow summaries.
Show a summary per file
File Description
setup/md/safe_outputs_prompt.md Adds file-body injection guidance
setup/md/mcp_cli_tools_prompt.md Documents jq -Rs payload creation
setup/js/update_pull_request.cjs Handles additional non-fatal API errors
setup/js/threat_detection_warning.cjs Classifies tooling failures
setup/js/safe_outputs_handlers.cjs Improves side-repository checkout detection
setup/js/messages_run_status.cjs Separates tooling and security warnings
setup/js/messages_footer.cjs Adds model and detection template fields
setup/js/install_frontmatter_skills.cjs Collapses skill-install summaries
setup/js/generate_footer.cjs Distinguishes tooling failure alerts
setup/js/check_command_position.cjs Corrects slash-command guidance

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 10/10 changed files
  • Comments generated: 2
  • Review effort level: Medium

temporary_id: optional cross-reference field for future resources created by safe outputs. Canonical form: '#aw_' followed by 3–12 alphanumeric or underscore characters — e.g., '#aw_abc1', '#aw_pr_fix'. Pattern: /^#?aw_[A-Za-z0-9_]{3,12}$/i (the '#' prefix is optional; bare 'aw_abc1' is accepted and normalised to '#aw_abc1' automatically). Use this form for all field values (temporary_id, item_number, issue_number, parent, etc.). In body/markdown text, '#aw_abc1' references are replaced with the real issue/PR number after creation. Omit entirely when not needed.

**Note**: safeoutputs tools do NOT support `@filename` file name expansion. Always provide content inline — do not use `@filename` references in tool arguments.
**Note**: safeoutputs tools do NOT support `@filename` file name expansion. Always provide content inline — do not use `@filename` references in tool arguments. To inject an entire file as the `body` field, use `jq -Rs` to read it as a JSON string and pipe the resulting payload: `jq -Rs '{body: .}' file.md | safeoutputs update_discussion .`
Comment on lines +157 to +158
const defaultTemplate = `> [!WARNING]\n> threat detection engine error\n> The threat detection engine encountered an error and could not complete analysis. This is a tooling failure, not a security finding.\n> ${getThreatDetectedMarkerTemplate()}\n>\n> <details>\n> <summary>Details</summary>\n>\n> {reason_text}\n>\n> Review the [workflow run logs]({run_url}) for details.\n> </details>`;
return renderConfiguredMessage("detectionEngineError", defaultTemplate, { ...ctx, reasonText, threatKinds: normalizeThreatKinds(ctx.reason) });
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants