Update go-fan workflow to create issues instead of discussions (#46)

Author: Copilot

.github/workflows/agentics-maintenance.yml

@@ -0,0 +1,135 @@
+#
+#    ___                   _   _      
+#   / _ \                 | | (_)     
+#  | |_| | __ _  ___ _ __ | |_ _  ___ 
+#  |  _  |/ _` |/ _ \ '_ \| __| |/ __|
+#  | | | | (_| |  __/ | | | |_| | (__ 
+#  \_| |_/\__, |\___|_| |_|\__|_|\___|
+#          __/ |
+#  _    _ |___/ 
+# | |  | |                / _| |
+# | |  | | ___ _ __ _  __| |_| | _____      ____
+# | |/\| |/ _ \ '__| |/ /|  _| |/ _ \ \ /\ / / ___|
+# \  /\  / (_) | | | | ( | | | | (_) \ V  V /\__ \
+#  \/  \/ \___/|_| |_|\_\|_| |_|\___/ \_/\_/ |___/
+#
+# This file was automatically generated by pkg/workflow/maintenance_workflow.go (v0.35.1). DO NOT EDIT.
+#
+# To regenerate this workflow, run:
+#   gh aw compile
+# For more information: https://github.com/githubnext/gh-aw/blob/main/.github/aw/github-agentic-workflows.md
+#
+# Alternative regeneration methods:
+# make recompile
+# 
+# Or use the gh-aw CLI directly:
+# ./gh-aw compile --validate --verbose
+# 
+# The workflow is generated when any workflow uses the 'expires' field
+# in create-discussions or create-issues safe-outputs configuration.
+# Schedule frequency is automatically determined by the shortest expiration time.
+#
+name: Agentics Maintenance
+
+on:
+  schedule:
+    - cron: "37 */2 * * *"  # Every 2 hours (based on minimum expires: 1 days)
+  workflow_dispatch:
+
+permissions: {}
+
+jobs:
+  close-expired-discussions:
+    runs-on: ubuntu-latest
+    permissions:
+      discussions: write
+    steps:
+      - name: Setup Scripts
+        uses: githubnext/gh-aw/actions/setup@v0.35.1
+        with:
+          destination: /tmp/gh-aw/actions
+
+      - name: Close expired discussions
+        uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
+        with:
+          script: |
+            const { setupGlobals } = require('/tmp/gh-aw/actions/setup_globals.cjs');
+            setupGlobals(core, github, context, exec, io);
+            const { main } = require('/tmp/gh-aw/actions/close_expired_discussions.cjs');
+            await main();
+
+  close-expired-issues:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - name: Setup Scripts
+        uses: githubnext/gh-aw/actions/setup@v0.35.1
+        with:
+          destination: /tmp/gh-aw/actions
+
+      - name: Close expired issues
+        uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
+        with:
+          script: |
+            const { setupGlobals } = require('/tmp/gh-aw/actions/setup_globals.cjs');
+            setupGlobals(core, github, context, exec, io);
+            const { main } = require('/tmp/gh-aw/actions/close_expired_issues.cjs');
+            await main();
+
+  compile-workflows:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+
+      - name: Setup Go
+        uses: actions/setup-go@41dfa10bad2bb2ae585af6ee5bb4d7d973ad74ed # v5.1.0
+        with:
+          go-version-file: go.mod
+          cache: true
+
+      - name: Build gh-aw
+        run: make build
+
+      - name: Compile workflows
+        run: |
+          ./gh-aw compile --validate --verbose
+          echo "✓ All workflows compiled successfully"
+
+      - name: Check for out-of-sync workflows
+        run: |
+          if git diff --exit-code .github/workflows/*.lock.yml; then
+            echo "✓ All workflow lock files are up to date"
+          else
+            echo "::error::Some workflow lock files are out of sync. Run 'make recompile' locally."
+            echo "::group::Diff of out-of-sync files"
+            git diff .github/workflows/*.lock.yml
+            echo "::endgroup::"
+            exit 1
+          fi
+
+  zizmor-scan:
+    runs-on: ubuntu-latest
+    needs: compile-workflows
+    permissions:
+      contents: read
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+
+      - name: Setup Go
+        uses: actions/setup-go@41dfa10bad2bb2ae585af6ee5bb4d7d973ad74ed # v5.1.0
+        with:
+          go-version-file: go.mod
+          cache: true
+
+      - name: Build gh-aw
+        run: make build
+
+      - name: Run zizmor security scanner
+        run: |
+          ./gh-aw compile --zizmor --verbose
+          echo "✓ Zizmor security scan completed"

.github/workflows/go-fan.lock.yml

@@ -26,11 +26,12 @@ imports:
   - shared/reporting.md
 
 safe-outputs:
-  create-discussion:
+  create-issue:
     title-prefix: "[go-fan] "
-    category: "General"
+    labels: [go-fan, module-review]
     max: 1
-    close-older-discussions: true
+    expires: 7
+  noop:
 
 tools:
   serena: ["go"]
@@ -247,9 +248,9 @@ Save your progress to cache-memory:
 
 This allows the round-robin to cycle through all dependencies while maintaining preference for recently updated ones.
 
-## Step 8: Create Discussion
+## Step 8: Create Issue
 
-Create a discussion summarizing your findings:
+Create an issue summarizing your findings:
 
 **Title Format**: `Go Module Review: <module-name>`
 
@@ -324,10 +325,14 @@ Use Serena for:
 
 ## Output
 
-Your output MUST include:
+Your output depends on whether improvements are found:
+
+**If improvements are found:**
 1. A module summary saved to `specs/mods/<module>.md`
-2. A discussion with your complete analysis and recommendations
+2. An issue with your complete analysis and recommendations
 
-If you cannot find any improvements, still create a discussion noting the module is well-utilized and document your analysis in `specs/mods/`.
+**If no improvements are found:**
+1. A module summary saved to `specs/mods/<module>.md` documenting your analysis
+2. Call the `noop` tool with a message like: "Go Module Review complete for <module-name> - module is well-utilized, no improvements identified at this time. Analysis saved to specs/mods/<module>.md"
 
 Begin your analysis! Pick the next module and start your deep review.