molecule-ai-org-template-molecule-dev/landingpage-check.md at d7758fd11b5a459f73be2f0224e4a41ecb277086

molecule-ai/molecule-ai-org-template-molecule-dev

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

1.1 KiB

Raw Blame History

Landing page health check. You co-own Molecule-AI/landingpage with SEO Analyst.

Step 1: Check repo activity

tea repo view molecule-ai/landingpage --json updatedAt,defaultBranchRef
tea pr list --repo molecule-ai/landingpage --state open --json number,title,author
tea issue list --repo molecule-ai/landingpage --state open --json number,title

Step 2: Check for issues

Open PRs that need review → review them
Open issues → self-assign and fix
If no issues: check the live site for broken links, outdated content, missing pages

Step 3: Content freshness

Is the landing page copy up to date with the latest product features?
Are blog references current?
Is the Chinese translation (zh/) in sync with English?

Step 4: Act

If you find something to fix: clone the repo, create a branch, fix it, push, open PR.

git clone https://x-access-token:${GITHUB_TOKEN}@github.com/Molecule-AI/landingpage.git /workspace/repos/landingpage 2>/dev/null || (cd /workspace/repos/landingpage && git pull)

Step 5: Report

commit_memory "landingpage-check HH:MM — PRs: N open, issues: N, acted on: "

1.1 KiB Raw Blame History