Skip to content

Commit cf62bef

Browse files
committed
feat(examples): support fallback to standard triage summary if custom instructions are omitted
1 parent 298d9d6 commit cf62bef

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

examples/workflows/issue-cleanup/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ The Issue Cleanup workflow is designed to automate the triage of stale issues by
88

99
1. **Check Code Validity**: Determines if an issue is still relevant against the current codebase. If the issue has already been resolved implicitly, it will close the issue with an explanation.
1010
2. **Find Duplicates**: Checks if the issue has a more recent duplicate. If a duplicate exists, it closes the issue and links to the duplicate.
11-
3. **Summarize for Triage**: If an issue is still valid and unique, it provides a summary comment based on customizable instructions (e.g., categorizing it as `Maintainer-only` or `Help-wanted`).
11+
3. **Summarize for Triage**: If an issue is still valid and unique, it provides a summary comment based on customizable instructions (e.g., categorizing it as `Maintainer-only` or `Help-wanted`). If no custom instructions are provided, it falls back to a standard triage summary (identifying the core problem, impact, and next steps).
1212

1313
## Usage
1414

examples/workflows/issue-cleanup/gemini-issue-cleanup.toml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,10 @@ You MUST use your tools (like `grep_search`, `read_file`, and `run_shell_command
3131
3232
### Step 3: Provide Triage Summary
3333
- If the issue is still valid and NOT a duplicate, add a brief summary comment for further triaging.
34-
- To formulate your summary, follow these custom instructions:
34+
- If custom instructions are provided below, use them to formulate your summary. Otherwise, formulate a standard triage summary (e.g., identifying the core problem, potential impact, and recommended next steps for a maintainer).
3535
```
3636
!{echo $CUSTOM_INSTRUCTIONS}
3737
```
38-
- Use `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n<your summary based on custom instructions>" --repo !{echo $REPOSITORY}`
38+
- Use `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n<your summary>" --repo !{echo $REPOSITORY}`
3939
- STOP execution. You are done with this issue.
4040
"""

0 commit comments

Comments
 (0)