fix: close merged submission issues

Author: Neikon

.github/workflows/close-merged-theme-submission.yml

@@ -0,0 +1,31 @@
+name: Close Merged Theme Submission Issue
+
+on:
+  pull_request:
+    types: [closed]
+
+permissions:
+  issues: write
+  pull-requests: read
+
+jobs:
+  close_issue:
+    if: ${{ github.event.pull_request.merged == true && startsWith(github.event.pull_request.head.ref, 'submissions/theme-') }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Close source issue
+        env:
+          GH_TOKEN: ${{ github.token }}
+          PR_BODY: ${{ github.event.pull_request.body }}
+          PR_NUMBER: ${{ github.event.pull_request.number }}
+        shell: bash
+        run: |
+          issue_number="$(printf '%s' "$PR_BODY" | sed -nE 's/^Generated from #([0-9]+)\.$/\1/p' | head -n 1)"
+
+          if [ -z "$issue_number" ]; then
+            echo "No source issue number found in PR #${PR_NUMBER}."
+            exit 0
+          fi
+
+          gh issue close "$issue_number" \
+            --comment "Theme submission was merged in #${PR_NUMBER}. Thanks for sharing it."

MEMORY.md

@@ -35,11 +35,13 @@ This file stores durable project context so future conversations can resume work
 - `.github/workflows/check-themes.yml`
 - `.github/workflows/create-theme-submission.yml`
 - `.github/workflows/publish-approved-theme-submission.yml`
+- `.github/workflows/close-merged-theme-submission.yml`
 - CI workflows now opt into Node 24 for JavaScript actions explicitly and use `actions/checkout@v6` plus `actions/setup-node@v6`
 - Build workflow runs automatically on pushes to `main` that affect Astro site/build inputs and deploys `dist/` through GitHub Pages artifacts
 - PR validation runs `npm test` and `npm run build` for site-related changes
 - Theme submission automation uses GitHub Issue Forms plus `.github/workflows/create-theme-submission.yml`; it creates candidate PRs from complete submission issues without Decap or external auth hosting
 - Approved submission PRs are finalized by `.github/workflows/publish-approved-theme-submission.yml`, which sets `status: "published"` and assigns the next available low `catalogIndex`; maintainers still merge the PR explicitly
+- Merged submission PRs close their source issue through `.github/workflows/close-merged-theme-submission.yml`; new generated PR bodies also include `Closes #<issue>`
 - The build workflow syntax also requires `workflow_dispatch:` with a trailing colon; missing it makes GitHub mark the workflow file as invalid even if other checks still pass
 
 ## Repo Notes

README.md

@@ -42,7 +42,7 @@ Community submissions use the `Submit a theme` GitHub Issue Form. When a complet
 - validate the catalog with `npm test` and `npm run build`;
 - open or update a review pull request from a `submissions/theme-<issue-number>` branch.
 
-The generated entry remains `status: "candidate"` until a maintainer approves the submission PR. Approval runs `.github/workflows/publish-approved-theme-submission.yml`, which switches the entry to `status: "published"` and assigns the next available `catalogIndex`. Maintainers still merge the PR explicitly after checks pass.
+The generated entry remains `status: "candidate"` until a maintainer approves the submission PR. Approval runs `.github/workflows/publish-approved-theme-submission.yml`, which switches the entry to `status: "published"` and assigns the next available `catalogIndex`. Maintainers still merge the PR explicitly after checks pass. Merged submission PRs close their source issue automatically.
 
 ## Metadata Refresh
 

scripts/create-theme-submission-from-issue.mjs

@@ -324,6 +324,8 @@ function prBody({ theme, notes, issueNumber, issueAuthor, screenshotUrls }) {
 
 Generated from #${issueNumber}.
 
+Closes #${issueNumber}.
+
 - Title: ${theme.title}
 - Slug: \`${theme.slug}\`
 - Repository: ${theme.repository}