Fix automated workflow not triggering with /process command (#777)

Copilot · web-flow · commit 42befab7aef9 · 2025-10-16T14:39:17.000-07:00
* Fix workflow trigger conditions and add comprehensive logging
diff --git a/.github/workflows/README.md b/.github/workflows/README.md
@@ -0,0 +1,79 @@
+# GitHub Workflows
+
+This directory contains automated workflows for the Web We Want project.
+
+## Process Want Submission Workflow
+
+The `process-want-submission.yml` workflow automates the processing of Want submissions.
+
+### Triggers
+
+The workflow is triggered by:
+
+1. **Netlify Form Submission** (`repository_dispatch` event)
+   - Automatically creates an issue from form submissions
+   - No manual intervention required
+
+2. **New Want Issue Opened** (`issues` event)
+   - Automatically processes issues with title starting with `[Auto] New Want:`
+   
+3. **Manual Processing via Comment** (`issue_comment` event)
+   - Any of the following commands in an issue comment will trigger the workflow:
+     - `/process` - Simple slash command
+     - `@github-copilot` - Mention Copilot
+     - `@github-copilot[bot] process` - Full mention with process keyword
+
+4. **PR Merged** (`pull_request` event with `closed` and `merged=true`)
+   - Converts the related issue to a discussion after a want PR is merged
+
+### Manual Processing
+
+To manually trigger want processing on an existing issue, add a comment with any of these commands:
+
+```
+/process
+```
+
+or
+
+```
+@github-copilot please process this want
+```
+
+The workflow will:
+1. Log trigger information for debugging
+2. Create a processing trigger comment
+3. Assign the issue to GitHub Copilot
+4. Copilot will follow the instructions in `.github/instructions/wants-processing.instructions.md`
+
+### Debugging
+
+If the workflow doesn't run as expected:
+
+1. Check the workflow run logs in the Actions tab
+2. Look for the "Log workflow trigger" step to see what event triggered the workflow
+3. Verify the issue title matches the expected pattern (for auto-generated issues)
+4. Ensure your comment contains one of the trigger keywords (for manual processing)
+
+### Workflow Steps
+
+1. **Log workflow trigger** - Logs information about what triggered the workflow
+2. **Checkout repository** - Checks out the code
+3. **Setup Node.js** - Installs Node.js environment
+4. **Install dependencies** - Installs npm packages
+5. **Create issue from webhook** - For Netlify form submissions
+6. **Process existing issue** - For manual triggers via comments
+7. **Assign to Copilot** - Creates a comment to trigger Copilot processing
+8. **Log completion** - Logs completion status
+
+### Processing Instructions
+
+The detailed processing instructions for GitHub Copilot are located in:
+`.github/instructions/wants-processing.instructions.md`
+
+This includes:
+- Spam detection
+- Relevance checking
+- Technology classification
+- Duplicate detection
+- Want file creation
diff --git a/.github/workflows/process-want-submission.yml b/.github/workflows/process-want-submission.yml
@@ -20,9 +20,26 @@ jobs:
     if: |
       github.event_name == 'repository_dispatch' || 
       (github.event_name == 'issues' && startsWith(github.event.issue.title, '[Auto] New Want:')) ||
-      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@github-copilot[bot]') && contains(github.event.comment.body, 'process-want'))
+      (github.event_name == 'issue_comment' && (
+        contains(github.event.comment.body, '/process') ||
+        contains(github.event.comment.body, '@github-copilot') ||
+        (contains(github.event.comment.body, '@github-copilot[bot]') && contains(github.event.comment.body, 'process'))
+      ))
     runs-on: ubuntu-latest
     steps:
+      - name: Log workflow trigger
+        run: |
+          echo "=== Workflow Trigger Information ==="
+          echo "Event name: ${{ github.event_name }}"
+          echo "Triggered by: ${{ github.actor }}"
+          echo "Repository: ${{ github.repository }}"
+          if [ "${{ github.event_name }}" = "issue_comment" ]; then
+            echo "Comment author: ${{ github.event.comment.user.login }}"
+            echo "Issue number: ${{ github.event.issue.number }}"
+            echo "Issue title: ${{ github.event.issue.title }}"
+            echo "Comment body (first 200 chars): ${{ github.event.comment.body }}" | head -c 200
+          fi
+          echo "==================================="
       - name: Checkout repository
         uses: actions/checkout@v4
         with:
@@ -121,15 +138,27 @@ jobs:
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           script: |
-            const issue = github.event_name === 'issue_comment' 
-              ? context.payload.issue 
-              : context.payload.issue;
-
-            const issueBody = issue.body;
+            console.log('=== Processing existing issue/comment ===');
+            console.log(`Event name: ${context.eventName}`);
+            console.log(`Issue number: ${context.payload.issue.number}`);
+            
+            const issue = context.payload.issue;
+            const issueBody = issue.body || '';
+            
+            console.log(`Issue title: ${issue.title}`);
+            console.log(`Issue body length: ${issueBody.length}`);
+            
             const submissionIdMatch = issueBody.match(/\*\*Submission ID:\*\* (.+)/);
             const submissionId = submissionIdMatch ? submissionIdMatch[1] : `manual-${issue.number}-${Date.now()}`;
-
-            if (github.event_name === 'issue_comment') {
+            
+            console.log(`Submission ID: ${submissionId}`);
+
+            if (context.eventName === 'issue_comment') {
+              console.log('Processing as issue comment event');
+              const comment = context.payload.comment;
+              console.log(`Comment author: ${comment.user.login}`);
+              console.log(`Comment body: ${comment.body.substring(0, 200)}`);
+              
               const commentBody = [
                 '## Manual Processing Triggered',
                 '',
@@ -150,12 +179,14 @@ jobs:
                 `Body: ${issueBody.substring(0, 500)}${issueBody.length > 500 ? '...' : ''}`
               ].join('\n');
 
+              console.log('Creating processing trigger comment...');
               await github.rest.issues.createComment({
                 owner: context.repo.owner,
                 repo: context.repo.repo,
                 issue_number: issue.number,
                 body: commentBody
               });
+              console.log('Processing trigger comment created successfully');
             }
 
             return {
@@ -168,9 +199,13 @@ jobs:
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           script: |
+            console.log('=== Assigning to Copilot ===');
+            console.log(`Event name: ${context.eventName}`);
+            
             // Get issue number from previous steps or current context
             let issueNumber;
-            if (github.event_name === 'repository_dispatch') {
+            if (context.eventName === 'repository_dispatch') {
+              console.log('Getting issue from repository_dispatch event');
               // For webhook events, we need to find the issue we just created
               // We'll use a simple approach and get the most recent issue
               const issues = await github.rest.issues.listForRepo({
@@ -183,16 +218,20 @@ jobs:
                 per_page: 1
               });
               issueNumber = issues.data[0]?.number;
+              console.log(`Found issue number: ${issueNumber}`);
             } else {
               // For issue events, use the issue from the event
               issueNumber = context.payload.issue.number;
+              console.log(`Using issue from event: ${issueNumber}`);
             }
 
             if (!issueNumber) {
-              console.log('Could not determine issue number');
+              console.log('ERROR: Could not determine issue number');
               return;
             }
 
+            console.log(`Creating Copilot trigger comment on issue #${issueNumber}`);
+            
             // Add comment to trigger Copilot processing
             await github.rest.issues.createComment({
               owner: context.repo.owner,
@@ -203,13 +242,22 @@ jobs:
               Follow the 5-step process: spam detection, relevance check, technology classification, duplicate detection, and want PR creation if approved.`
             });
 
-            console.log(`Issue ${issueNumber} has been assigned to Copilot for processing`);
+            console.log(`Successfully assigned issue ${issueNumber} to Copilot for processing`);
 
       - name: Log processing completion
         run: |
-          echo "Want submission processing workflow completed"
-          echo "Check GitHub Actions logs for issue details"
-          echo "Workflow triggered for submission processing"
+          echo "==================================="
+          echo "Want submission processing workflow completed successfully"
+          echo "Event: ${{ github.event_name }}"
+          echo "Triggered by: ${{ github.actor }}"
+          echo "Repository: ${{ github.repository }}"
+          echo "==================================="
+          echo ""
+          echo "Next steps:"
+          echo "- Check the issue for Copilot's processing comments"
+          echo "- Review any PR created by Copilot"
+          echo "- Check GitHub Actions logs for detailed execution trace"
+          echo "==================================="
 
   convert-issue-to-discussion:
     if: github.event_name == 'pull_request' && github.event.pull_request.merged == true
diff --git a/docs/MANUAL_PROCESSING.md b/docs/MANUAL_PROCESSING.md
@@ -14,7 +14,11 @@ Use manual processing for:
 ### Method 1: Issue Comment Trigger
 
 1. Navigate to the GitHub issue you want to process
-2. Add a comment with the text `/process-want` or `/process`
+2. Add a comment with one of these trigger commands:
+   - `/process` - Simple slash command
+   - `/process-want` - Alternative slash command
+   - `@github-copilot` - Mention Copilot directly
+   - `@github-copilot[bot] please process this want` - Full mention with instruction
 3. The workflow will automatically trigger and process the issue
 
 ### Method 2: Repository Dispatch (for bulk processing)
@@ -87,8 +91,10 @@ The manual processing can result in several outcomes:
 
 ### Workflow Doesn't Trigger
 - Ensure you have proper repository permissions
-- Check that the comment contains a trigger phrase
+- Check that the comment contains a trigger phrase (e.g., `/process`, `@github-copilot`)
 - Verify the workflow file is present and valid
+- Check the Actions tab to see if the workflow was skipped and review the logs
+- Review `.github/workflows/README.md` for trigger requirements
 
 ### Processing Fails
 - Check the Actions tab for error details
