molecule-ai/molecule-ai-org-template-molecule-dev
35
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
da5058caa8
molecule-ai-org-template-mo.../dev-lead/schedules/pr-shepherd.md
documentation-specialist d7758fd11b
Some checks are pending
CI / validate (push) Waiting to run
Details
fix(personas): migrate gh CLI → tea (Gitea CLI) + curl-via-API (#45) 
Mass-sed across all 58 persona dirs in molecule-ai-org-template-molecule-dev.

Total: 158 files / 396 substitutions
- 389 gh → tea mappings (gh pr/issue/repo/run/auth → tea pr/issue/repo/action/login)
- 7 gh api → curl-via-API mappings
- All Molecule-AI/<repo> → molecule-ai/<repo> in --repo flags (Gitea slug case-sensitive)

Plus SHARED_RULES.md migration callout block + tea install snippet:
- Tea v0.9.2 install via wget (Q2 = B per orchestrator: per-job, not pre-baked into runner image)
- Authenticate using GITEA_TOKEN env var (gating on internal#44 workspace-bootstrap injection)
- Two known limitations called out:
  1. GITEA_TOKEN required for tea/curl auth (internal#44 pending)
  2. tea is per-job-installed; pre-bake parked for image-v2 work
- Cross-link to internal#45 for additions

Two manual edge cases:
- gh search code (no tea equivalent) → curl + tea repo clone + grep recipe
- URL with mixed-case Molecule-AI → lowercase molecule-ai (Gitea case-sensitive)

3 narrative GH_TOKEN references in SHARED_RULES.md intentionally preserved
(describe an env var name, not commands).

Q1=A (mega-PR) per orchestrator dispatch 2026-05-07T09:50:08.

Refs: molecule-ai/internal#45, molecule-ai/internal#44 (GITEA_TOKEN dep)
2026-05-07 02:54:35 -07:00

761 B
Raw Blame History

PR REVIEW SHEPHERD — your job is to ensure open PRs get reviewed and merged, not abandoned.

  1. List all open PRs: tea pr list --repo molecule-ai/molecule-core --state open --json number,title,createdAt,author
  2. For each PR older than 6 hours:
    • Check CI status: tea pr checks
    • If CI green: review the diff, approve if safe, merge it
    • If CI red: check the failure, fix it on the branch if you can, or close with explanation
    • If superseded by another PR: close with comment linking to the replacement
  3. Close duplicate PRs (same fix attempted multiple times)
  4. Report: commit_memory "pr-shepherd HH:MM — reviewed N PRs, merged M, closed K"

RULE: Old PRs are a defect signal. Every PR should either merge or close within 24 hours.