Remove emojis from agent failure messages

actions/setup/md/agent_failure_issue.md

@@ -11,7 +11,7 @@
 **Assign this issue to Copilot** using the `agentic-workflows` sub-agent to automatically debug and fix the workflow failure.
 
 <details>
-<summary><b>🤖 Debug with any coding agent</b></summary>
+<summary><b>Debug with any coding agent</b></summary>
 
 Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
 
@@ -24,7 +24,7 @@ The failed workflow run is at {run_url}
 </details>
 
 <details>
-<summary><b>🛠️ Manually invoke the agent</b></summary>
+<summary><b>Manually invoke the agent</b></summary>
 
 Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.
 

actions/setup/md/agent_timeout.md

@@ -1,4 +1,4 @@
-**⏱️ Agent Timed Out**: The agent job exceeded the maximum allowed execution time ({current_minutes} minutes).
+**Agent Timed Out**: The agent job exceeded the maximum allowed execution time ({current_minutes} minutes).
 
 To increase the timeout, add or update the `timeout-minutes` setting in your workflow's frontmatter:
 

actions/setup/md/app_token_minting_failed.md

@@ -1,4 +1,4 @@
-**🔑 GitHub App Authentication Failed**: Failed to generate a GitHub App installation access token.
+**GitHub App Authentication Failed**: Failed to generate a GitHub App installation access token.
 
 This is typically caused by an incorrect GitHub App configuration. Please verify:
 - The **App ID** secret/variable is set correctly

actions/setup/md/assign_copilot_to_created_issues_failure.md

@@ -1,5 +1,5 @@
 
-**🤖 Copilot Assignment Failed**: The workflow created an issue but could not assign the Copilot coding agent to it. This typically happens when:
+**Copilot Assignment Failed**: The workflow created an issue but could not assign the Copilot coding agent to it. This typically happens when:
 
 - The `GH_AW_AGENT_TOKEN` secret is missing or has expired
 - The token does not have the `issues: write` permission

actions/setup/md/inference_access_error.md

@@ -1,5 +1,5 @@
 
-**🔑 Inference Access Denied**: The Copilot CLI failed because the token does not have access to inference. This can happen when:
+**Inference Access Denied**: The Copilot CLI failed because the token does not have access to inference. This can happen when:
 
 - Your organization has restricted Copilot access
 - The `COPILOT_GITHUB_TOKEN` does not have a valid Copilot subscription

actions/setup/md/lockdown_check_failed.md

@@ -1,4 +1,4 @@
-**🔒 Lockdown Check Failed**: The workflow could not start because its security requirements were not met.
+**Lockdown Check Failed**: The workflow could not start because its security requirements were not met.
 
 This can happen when:
 

actions/setup/md/manifest_protection_create_pr_fallback.md

@@ -3,14 +3,14 @@
 ---
 
 > [!WARNING]
-> 🛡️ **Protected Files**
+> **Protected Files**
 >
 > This was originally intended as a pull request, but the patch modifies protected files. These files may affect project dependencies, CI/CD pipelines, or agent behaviour. **Please review the changes carefully** before creating the pull request.
 >
 > **[Click here to create the pull request once you have reviewed the changes]({create_pr_url})**
 
 <details>
-<summary>🔒 Protected files</summary>
+<summary>Protected files</summary>
 
 {files}
 

actions/setup/md/manifest_protection_push_failed_fallback.md

@@ -3,12 +3,12 @@
 ---
 
 > [!WARNING]
-> 🛡️ **Protected Files — Push Permission Denied**
+> **Protected Files — Push Permission Denied**
 >
 > This was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.
 
 <details>
-<summary>🔒 Protected files</summary>
+<summary>Protected files</summary>
 
 {files}
 
@@ -17,7 +17,7 @@ The push was rejected because GitHub Actions does not have `workflows` permissio
 </details>
 
 <details>
-<summary><b>📋 Create the pull request manually</b></summary>
+<summary><b>Create the pull request manually</b></summary>
 
 ```sh
 # Download the patch from the workflow run

actions/setup/md/manifest_protection_push_to_pr_fallback.md

@@ -1,5 +1,5 @@
 > [!WARNING]
-> 🛡️ **Protected Files**
+> **Protected Files**
 >
 > The push to pull request branch was blocked because the patch modifies protected files.
 >
@@ -8,7 +8,7 @@
 > **Please review the changes carefully** before pushing them to the pull request branch. These files may affect project dependencies, CI/CD pipelines, or agent behaviour.
 
 <details>
-<summary>🔒 Protected files</summary>
+<summary>Protected files</summary>
 
 {files}
 
@@ -17,7 +17,7 @@
 ---
 
 <details>
-<summary><b>📋 Apply the patch after review</b></summary>
+<summary><b>Apply the patch after review</b></summary>
 
 The patch is available in the workflow run artifacts:
 

actions/setup/md/noop_runs_issue.md

@@ -1,7 +1,7 @@
 This issue tracks all no-op runs from agentic workflows in this repository. Each workflow run that completes with a no-op message (indicating no action was needed) posts a comment here.
 
 <details>
-<summary><b>📘 What is a No-Op?</b></summary>
+<summary><b>What is a No-Op?</b></summary>
 
 A no-op (no operation) occurs when an agentic workflow runs successfully but determines that no action is required. For example:
 - A security scanner that finds no issues
@@ -13,7 +13,7 @@ These are successful outcomes, not failures, and help provide transparency into
 </details>
 
 <details>
-<summary><b>🎯 How This Helps</b></summary>
+<summary><b>How This Helps</b></summary>
 
 This issue helps you:
 - Track workflows that ran but determined no action was needed
@@ -23,7 +23,7 @@ This issue helps you:
 </details>
 
 <details>
-<summary><b>📚 Resources</b></summary>
+<summary><b>Resources</b></summary>
 
 - [GitHub Agentic Workflows Documentation](https://github.com/github/gh-aw)
 

actions/setup/md/pr_checkout_failure.md

@@ -1,4 +1,4 @@
-## ❌ Failed to Checkout PR Branch
+## Failed to Checkout PR Branch
 
 **Error:** {error_message}