Skip to content

Merge: promote staging → main — set GITHUB_TOKEN on prod Convex#164

Merged
DIodide merged 1 commit into
mainfrom
staging
Jul 5, 2026
Merged

Merge: promote staging → main — set GITHUB_TOKEN on prod Convex#164
DIodide merged 1 commit into
mainfrom
staging

Conversation

@DIodide

@DIodide DIodide commented Jul 5, 2026

Copy link
Copy Markdown
Owner

Promotes the frontend-cd change (#163) so the prod Convex deployment (incredible-otter-96) gets GITHUB_TOKEN set on its next deploy — fixing skill-repo import on harness.nz. Staging already verified: the 'Set Convex GITHUB_TOKEN' deploy step succeeded there.

…-cd (#163)

The skill-repo import (convex/skills.ts: listRepoSkills / importSkillRepo /
ensureSkillDetails) calls the GitHub API from Convex egress. Without a
GITHUB_TOKEN env var on the deployment it shares the anonymous 60/req/hr limit
and fails (the browse dialog shows a rate-limit error / no skills).

The token had never been set on the app's real Convex deployment
(incredible-otter-96): a manual `convex env set --prod` from this repo targets
a DIFFERENT project (dusty-echidna-658) that the repo happens to be linked to,
not the one CONVEX_DEPLOY_KEY / VITE_CONVEX_URL point at. Fix it the durable
way: right after `convex deploy`, set GITHUB_TOKEN on the SAME deployment the
deploy key targets (prod on main, staging otherwise) from the existing
SKILLS_GITHUB_TOKEN secret. Idempotent, rotates with the secret, fail-soft
when unset. Mirrors the FastAPI host token step (#160).
@DIodide
DIodide merged commit 471b22a into main Jul 5, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant