From babddf2d1ef05093022489a73a13d96760519122 Mon Sep 17 00:00:00 2001 From: Steven Nguyen Date: Wed, 12 Nov 2025 11:49:58 -0800 Subject: [PATCH] fix: clarify bold formatting in triage instructions --- .github/workflows/issue-triage.lock.yml | 6 +++--- .github/workflows/issue-triage.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/issue-triage.lock.yml b/.github/workflows/issue-triage.lock.yml index 0813baf008..e2483cf0fd 100644 --- a/.github/workflows/issue-triage.lock.yml +++ b/.github/workflows/issue-triage.lock.yml @@ -5,7 +5,7 @@ # # Source: githubnext/agentics/workflows/issue-triage.md@0837fb7b24c3b84ee77fb7c8cfa8735c48be347a # -# Effective stop-time: 2025-12-12 18:55:25 +# Effective stop-time: 2025-12-12 19:43:36 # # Job Dependency Graph: # ```mermaid @@ -2200,7 +2200,7 @@ jobs: - Suggest resources or links that might be helpful for resolving the issue or learning skills related to the issue or the particular area of the codebase affected by it - Mention any nudges or ideas that could help the team in addressing the issue - If appropriate break the issue down to sub-tasks and write a checklist of things to do - - Use collapsed-by-default sections in the GitHub markdown to keep the comment tidy. Collapse all sections except the short main summary at the top. Ensure text is bolded using markdown syntax. + - Use collapsed-by-default sections in the GitHub markdown to keep the comment tidy. Collapse all sections except the short main summary at the top. For bolded section titles, wrap the text with `` and `` to make it bold. - Do not indicate/encourage a community member to submit a PR for the issue. 12. After processing all issues, provide a summary of how many issues were triaged (created or updated in the last 24 hours). If no issues matched the criteria, simply note that no issues needed triage. @@ -5007,7 +5007,7 @@ jobs: id: check_stop_time uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd env: - GH_AW_STOP_TIME: 2025-12-12 18:55:25 + GH_AW_STOP_TIME: 2025-12-12 19:43:36 GH_AW_WORKFLOW_NAME: "Agentic Triage" with: script: | diff --git a/.github/workflows/issue-triage.md b/.github/workflows/issue-triage.md index 448ee563cb..8b327a26cf 100644 --- a/.github/workflows/issue-triage.md +++ b/.github/workflows/issue-triage.md @@ -109,7 +109,7 @@ You're a triage assistant for GitHub issues. Your task is to analyze issues that - Suggest resources or links that might be helpful for resolving the issue or learning skills related to the issue or the particular area of the codebase affected by it - Mention any nudges or ideas that could help the team in addressing the issue - If appropriate break the issue down to sub-tasks and write a checklist of things to do - - Use collapsed-by-default sections in the GitHub markdown to keep the comment tidy. Collapse all sections except the short main summary at the top. Ensure text is bolded using markdown syntax. + - Use collapsed-by-default sections in the GitHub markdown to keep the comment tidy. Collapse all sections except the short main summary at the top. For bolded section titles, wrap the text with `` and `` to make it bold. - Do not indicate/encourage a community member to submit a PR for the issue. 12. After processing all issues, provide a summary of how many issues were triaged (created or updated in the last 24 hours). If no issues matched the criteria, simply note that no issues needed triage.