Add auto-add-repo workflow to process repo request issues

[jonathanpopham]

Context

Issue #4 is a repo request for narsil-mcp that has been sitting unprocessed. We need a workflow that automatically handles [Repo Request] issues - validates the repo, forks it into the org, sets up arch-docs, and adds it to repos.yaml.

Requirements

Create .github/workflows/auto-add-repo.yml that triggers on issues opened/edited when the title matches [Repo Request].

Steps the workflow should perform:

1. Parse the issue - extract the GitHub repo URL or owner/repo from the issue body
2. Validate the repo: must be public, not archived, not empty, not already in org or repos.yaml
3. Fork into the org with gh repo fork
4. Set up arch-docs workflow on the fork (use supermodeltools/arch-docs action)
5. Add to repos.yaml in the Community category with upstream, description, and language pill
6. Comment on the issue with success/failure status
7. Close the issue on success

Error handling:

• Repo not found or private: comment with error, label invalid
• Already in org: comment noting it exists, close issue
• Fork fails: comment with error details

Concurrency

Use concurrency group add-repo with cancel-in-progress: false (same as sync-repos).

Secrets

Needs BOT_TOKEN (same as issue 8) for forking and pushing.

Reference

A previous version existed in commit fa6acbf. Check with git show to find the original implementation.

Acceptance criteria

• Opening an issue titled [Repo Request] some-repo triggers the workflow
• Valid repos get forked, arch-docs installed, added to repos.yaml
• Issue gets a status comment and is closed on success
• Invalid requests get helpful error messages
• Issue 4 (narsil-mcp) can be processed by this workflow

@claude

[coderabbitai]

🔗 Related PRs

#3 - Add 'Request a Repo' button and issue template [closed]
#5 - Inline submit — no page navigation, everything in background [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[claude]

Working on Issue #9

• Gather context and read the issue
• Check commit fa6acbf for previous implementation
• Write .github/workflows/auto-add-repo.yml
• Commit changes locally
• Attempt push — blocked (token lacks workflow scope)

Manual Push Required

I've reconstructed auto-add-repo.yml from commit fa6acbf and committed it locally on branch claude/issue-9-20260303-1857. The GitHub App token can't push workflow files — you need to push from your terminal:

git fetch origin claude/issue-9-20260303-1857
git checkout claude/issue-9-20260303-1857
git push origin claude/issue-9-20260303-1857

Then open a PR from claude/issue-9-20260303-1857 to main.

What the workflow does

Recovered from fa6acbf:

1. Triggers on issues with the repo-request label
2. Parses GitHub URL from issue body
3. Validates: public, not archived, not empty, not duplicate
4. Auto-detects description, language, stars from GitHub API
5. Maps language to pill color
6. Forks repo into supermodeltools org
7. Sets SUPERMODEL_API_KEY secret on the fork
8. Installs arch-docs workflow via GitHub Contents API
9. Enables GitHub Pages on the fork
10. Appends to repos.yaml Community category using yq
11. Commits and pushes with BOT_TOKEN (triggers homepage rebuild)
12. Comments success/failure on the issue and closes it

Required secrets: BOT_TOKEN (PAT with repo + admin:org + workflow scopes) and SUPERMODEL_API_KEY

After merging, re-trigger issue #4 (narsil-mcp) by adding the repo-request label to it.

View job run

[jonathanpopham]

@claude The workflow scope issue is now fixed (BOT_TOKEN with workflow scope added). Please implement this issue — create a PR with the auto-add-repo workflow.

[jonathanpopham]

Claude finished @jonathanpopham's task in 7m 22s —— View job • claude/issue-9-20260303-2011 • [Create PR ➔](https://github.com/supermodeltools/supermodeltools.github.io/compare/main...claude/issue-9-20260303-2011?quick_pull=1&title=Issue%20%239%3A%20Changes%20from%20Claude&body=This%20PR%20addresses%20issue%20%239%0A%0AGenerated%20with%20%5BClaude%20Code%5D(https%3A%2F%2Fclaude.ai%2Fcode)

---

Done

• Gather context and read the issue
• Check commit fa6acbf — not in shallow clone; reconstructed from issue requirements
• Review existing workflows and repos.yaml for reference
• Write .github/workflows/auto-add-repo.yml
• Commit and push
• Create PR — #16

What the workflow does

Triggers on any issue opened/edited with a title starting [Repo Request].

1. Parses the GitHub URL or owner/repo from the issue body
2. Validates the repo is public, not archived, not empty, and not already present
3. Forks into supermodeltools org via gh repo fork
4. Installs the arch-docs workflow on the fork via GitHub Contents API
5. Sets SUPERMODEL_API_KEY secret on the fork
6. Enables GitHub Pages on the fork (best-effort)
7. Appends the entry to the Community category in repos.yaml, commits, and pushes (triggers homepage rebuild)
8. Comments success/failure on the issue and closes it on success

To process issue #4 (narsil-mcp) after merging: edit the issue title to re-save it — the edited event will retrigger the workflow.

PR #16 ·