feat(examples): check for resolved comments before asking for repro, and remove project tracking skip

Author: cocosheng-g

examples/workflows/issue-cleanup/README.md

@@ -6,8 +6,8 @@ This document describes a workflow to batch-process and clean up older open issu
 
 The Issue Cleanup workflow is designed to automate the triage of stale issues by using the Gemini CLI to:
 
-1. **Check for Projects and Parent Issues (Native)**: Identifies if an issue is already part of a GitHub Project or tracked by a parent issue (task list). If so, it removes the triage label and stops, assuming the issue is already being managed as part of a larger epic. If it has no assignees, it additionally asks the reporter if it is still needed (for feature requests) or asks them to try reproducing it with the latest build (for other issues).
-2. **Check for Staleness and Age (Native)**: Identifies if an issue has been waiting for reporter feedback for over 7 days, closing it if so. If the issue is not stale but hasn't been updated in over a month, it asks the reporter to reproduce it with the latest build. For feature requests, it asks to reopen if still needed. By default, it closes the inactive issue and tags any assignees to reopen it. However, if the issue is a high-priority (`p0` or `p1`), it leaves the issue open. This logic runs natively to save AI resources.
+1. **Check for Parent Issues (Native)**: Identifies if an issue is tracked by a parent issue (task list). If so, it removes the triage label and stops, assuming the issue is already being managed as part of a larger epic. If it has no assignees, it additionally asks the reporter if it is still needed (for feature requests) or asks them to try reproducing it with the latest build (for other issues).
+2. **Check for Staleness and Age (Native)**: Identifies if an issue has been waiting for reporter feedback for over 7 days, closing it if so. If the issue is not stale but hasn't been updated in over a month, it first checks if the last comment indicates the issue is resolved (e.g., "functioning properly"); if so, it closes it as completed. Otherwise, it asks the reporter to reproduce it with the latest build. For feature requests, it asks to reopen if still needed. By default, it closes the inactive issue as "not planned" and tags any assignees to reopen it. However, if the issue is a high-priority (`p0` or `p1`), it leaves the issue open. This logic runs natively to save AI resources.
 3. **Check for Vagueness (AI)**: If an issue is not stale or old but lacks sufficient information (e.g., reproduction steps), the agent asks the reporter for specific details and stops.
 4. **Check Code Validity (AI)**: Determines if an issue is still relevant against the current codebase. The agent may attempt to write and execute a minimal reproduction script to verify if a bug has been resolved, or manually inspect the code. If verified as fixed, it will close the issue with an explanation.
 5. **Find Duplicates (AI)**: Checks if the issue has a more recent duplicate. If a duplicate exists, it closes the issue and links to the duplicate.

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

@@ -86,17 +86,14 @@ jobs:
             });
             const reporter = issue.user.login;
 
-            // First, check if it's tracked by a parent issue or part of a project
+            // First, check if it's tracked by a parent issue
             const query = `
               query($owner: String!, $repo: String!, $issueNumber: Int!) {
                 repository(owner: $owner, name: $repo) {
                   issue(number: $issueNumber) {
                     trackedInIssues(first: 1) {
                       totalCount
                     }
-                    projectItems(first: 1) {
-                      totalCount
-                    }
                   }
                 }
               }
@@ -108,10 +105,9 @@ jobs:
                 issueNumber: issueNumber
               });
               const isTracked = result.repository.issue.trackedInIssues.totalCount > 0;
-              const inProject = result.repository.issue.projectItems.totalCount > 0;
               
-              if (isTracked || inProject) {
-                console.log(`Issue #${issueNumber} is tracked by a parent issue or project. Removing 'status/need-triage' and stopping.`);
+              if (isTracked) {
+                console.log(`Issue #${issueNumber} is tracked by a parent issue. Removing 'status/need-triage' and stopping.`);
                 try {
                   await github.rest.issues.removeLabel({
                     owner: context.repo.owner,
@@ -135,9 +131,9 @@ jobs:
                 if (!hasAssignees) {
                   let commentBody = '';
                   if (isFeatureRequest) {
-                    commentBody = `@${reporter}, this feature request is currently tracked by an epic or project but has no assignees. Could you please let us know if this is still needed?`;
+                    commentBody = `@${reporter}, this feature request is currently tracked by an epic but has no assignees. Could you please let us know if this is still needed?`;
                   } else {
-                    commentBody = `@${reporter}, this issue is currently tracked by an epic or project but has no assignees. Could you please try reproducing it with the latest build and let us know if it still occurs?`;
+                    commentBody = `@${reporter}, this issue is currently tracked by an epic but has no assignees. Could you please try reproducing it with the latest build and let us know if it still occurs?`;
                   }
                   await github.rest.issues.createComment({
                     owner: context.repo.owner,
@@ -151,7 +147,7 @@ jobs:
                 return;
               }
             } catch (err) {
-              console.log('Failed to fetch GraphQL data for parent issues/projects:', err.message);
+              console.log('Failed to fetch GraphQL data for parent issues:', err.message);
             }
 
             const { data: comments } = await github.rest.issues.listComments({
@@ -202,6 +198,30 @@ jobs:
             console.log(`Issue was last updated ${lastUpdateDaysAgo.toFixed(1)} days ago.`);
 
             if (lastUpdateDaysAgo > 30) {
+              // Check if the last comment says it's fixed
+              if (comments.length > 0) {
+                const lastCommentBody = comments[comments.length - 1].body.toLowerCase();
+                const resolvedKeywords = ['functioning properly', 'works now', 'is fixed', 'resolved now'];
+                if (resolvedKeywords.some(kw => lastCommentBody.includes(kw))) {
+                  console.log(`Issue appears resolved in the last comment. Closing.`);
+                  await github.rest.issues.createComment({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    issue_number: issueNumber,
+                    body: "Closing because the latest comments indicate this issue has been resolved. Feel free to reopen if the problem persists."
+                  });
+                  await github.rest.issues.update({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    issue_number: issueNumber,
+                    state: 'closed',
+                    state_reason: 'completed'
+                  });
+                  core.setOutput('is_stale', 'true');
+                  return;
+                }
+              }
+
               console.log(`Issue has been inactive for over a month. Asking for repro.`);
               
               try {