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

refactor: Simplify issue retrieval - use single since query

Browse Source 
The list_issues tool's 'since' parameter already filters by updated_at,
which captures both newly created issues AND recently commented issues in
a single query. Removed redundant second query.
This commit is contained in:
Steven Nguyen
2025-11-07 12:28:14 -08:00
parent b225503dc5
commit 09933ce658
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/issue-triage.lock.yml
Generated
+3 -3
View File
@@ -5,7 +5,7 @@
#
# Source: githubnext/agentics/workflows/issue-triage.md@0837fb7b24c3b84ee77fb7c8cfa8735c48be347a
#
# Effective stop-time: 2025-12-07 20:26:06
# Effective stop-time: 2025-12-07 20:28:14
#
# Job Dependency Graph:
# ```mermaid
@@ -2137,7 +2137,7 @@ jobs:
You're a triage assistant for GitHub issues. Your task is to analyze issues that were either created in the last 24 hours or updated (with a new comment) in the last 24 hours, and perform initial triage tasks for each of them.
1. First, use the `list_issues` tool to retrieve all issues created in the last 24 hours. Filter issues by using the `since` parameter with a timestamp from 24 hours ago (calculate: 2025-11-06T20:20:55.649Z for reference, subtract 24 hours). Additionally, retrieve issues that were updated in the last 24 hours using a separate query with the `since` parameter to capture recently commented issues.
1. First, use the `list_issues` tool to retrieve all issues created or updated in the last 24 hours. The `since` parameter filters by the issue's `updated_at` timestamp, which includes both newly created issues and recently commented issues. Calculate the timestamp from 24 hours ago (example: 2025-11-06T20:27:14Z for reference) and use it for the `since` parameter.
2. For each issue found, perform the following triage tasks:
@@ -5004,7 +5004,7 @@ jobs:
id: check_stop_time
uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd
env:
GH_AW_STOP_TIME: 2025-12-07 20:26:06
GH_AW_STOP_TIME: 2025-12-07 20:28:14
GH_AW_WORKFLOW_NAME: "Agentic Triage"
with:
script: |
.github/workflows/issue-triage.md
+1 -1
View File
@@ -46,7 +46,7 @@ source: githubnext/agentics/workflows/issue-triage.md@0837fb7b24c3b84ee77fb7c8cf
You're a triage assistant for GitHub issues. Your task is to analyze issues that were either created in the last 24 hours or updated (with a new comment) in the last 24 hours, and perform initial triage tasks for each of them.
1. First, use the `list_issues` tool to retrieve all issues created in the last 24 hours. Filter issues by using the `since` parameter with a timestamp from 24 hours ago (calculate: 2025-11-06T20:20:55.649Z for reference, subtract 24 hours). Additionally, retrieve issues that were updated in the last 24 hours using a separate query with the `since` parameter to capture recently commented issues.
1. First, use the `list_issues` tool to retrieve all issues created or updated in the last 24 hours. The `since` parameter filters by the issue's `updated_at` timestamp, which includes both newly created issues and recently commented issues. Calculate the timestamp from 24 hours ago (example: 2025-11-06T20:27:14Z for reference) and use it for the `since` parameter.
2. For each issue found, perform the following triage tasks: