Appwrite/appwrite
1
0
Fork 0
mirror of https://github.com/appwrite/appwrite.git synced 2026-05-26 13:51:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: Use GitHub MCP list_labels tool instead of bash gh command

Browse Source 
- Replace 'gh label list' bash command instruction with 'list_labels' GitHub MCP tool
- GitHub MCP tools are already enabled and authenticated, no additional config needed
- Fixes permission denied errors when agent tried to use gh CLI
This commit is contained in:
Steven Nguyen
2025-11-06 14:33:24 -08:00
parent 2f255ce01c
commit 2e4397a951
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/issue-triage.lock.yml
Generated
+4 -4
View File
@@ -5,7 +5,7 @@
#
# Source: githubnext/agentics/workflows/issue-triage.md@0837fb7b24c3b84ee77fb7c8cfa8735c48be347a
#
# Effective stop-time: 2025-12-06 19:47:58
# Effective stop-time: 2025-12-06 22:33:07
#
# Job Dependency Graph:
# ```mermaid
@@ -2141,13 +2141,13 @@ jobs:
2. For each issue found, perform the following triage tasks:
3. Select appropriate labels for the issue from the provided list.
3. Select appropriate labels for the issue from the provided list. Only apply the `good first issue` label on verified issues with straightforward fixes.
4. Retrieve the issue content using the `get_issue` tool. If the issue is obviously spam, or generated by bot, or something else that is not an actual issue to be worked on, then add an issue comment to the issue with a one sentence analysis and move to the next issue.
5. Next, use the GitHub tools to gather additional context about the issue:
- Fetch the list of labels available in this repository. Use 'gh label list' bash command to fetch the labels. This will give you the labels you can use for triaging issues.
- Fetch the list of labels available in this repository using the `list_labels` GitHub tool. This will give you the labels you can use for triaging issues.
- Fetch any comments on the issue using the `get_issue_comments` tool
- **Search for duplicate and related issues**: Use the `search_issues` tool to find similar issues by searching for key terms from the issue title and description. Look for both open and closed issues that might be related or duplicates.
@@ -4938,7 +4938,7 @@ jobs:
id: check_stop_time
uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd
env:
GH_AW_STOP_TIME: 2025-12-06 19:47:58
GH_AW_STOP_TIME: 2025-12-06 22:33:07
GH_AW_WORKFLOW_NAME: "Agentic Triage"
with:
script: |
.github/workflows/issue-triage.md
+2 -2
View File
@@ -45,13 +45,13 @@ You're a triage assistant for GitHub issues. Your task is to analyze issues crea
2. For each issue found, perform the following triage tasks:
3. Select appropriate labels for the issue from the provided list.
3. Select appropriate labels for the issue from the provided list. Only apply the `good first issue` label on verified issues with straightforward fixes.
4. Retrieve the issue content using the `get_issue` tool. If the issue is obviously spam, or generated by bot, or something else that is not an actual issue to be worked on, then add an issue comment to the issue with a one sentence analysis and move to the next issue.
5. Next, use the GitHub tools to gather additional context about the issue:
- Fetch the list of labels available in this repository. Use 'gh label list' bash command to fetch the labels. This will give you the labels you can use for triaging issues.
- Fetch the list of labels available in this repository using the `list_labels` GitHub tool. This will give you the labels you can use for triaging issues.
- Fetch any comments on the issue using the `get_issue_comments` tool
- **Search for duplicate and related issues**: Use the `search_issues` tool to find similar issues by searching for key terms from the issue title and description. Look for both open and closed issues that might be related or duplicates.