VersionControl:PRs/maybelle-config/246

maybelle-config#246: memory-lane: pass a read-only GitHub token (memory_lane_github_token) when the vault has one

State	🔴 closed 2026-11-07 00:40:16
Worked on by	magent, justin
Moods	#interfaces
Deploy	redeploy maybelle (after the vault has memory_lane_github_token)
Branch	memory-lane-github-token → production, by magent-cryptograss
Opened · last pushed	2026-10-31 17:51:20 · 2026-10-31 17:51:15

Justin, 31 Oct in #interfaces: merge asks for #295, #299 and #318 were still showing after #317 was deployed. The deployed memory-lane is f09c222, which includes #317.

**Likely cause.** memory-lane gets no `GITHUB_TOKEN`; the token in `maybelle.yml` goes only to Jenkins. Unsigned requests are limited to 60 GitHub calls an hour per IP, and maybelle spends them on to-do ticks, merge asks, PR cards (#314, deployed in the same release), work search and status. Right now `/api/status/` shows `pickipedia_mcp.error: "could not query GitHub: HTTPError"`. The same check (`todo._merged`) run from hunter says #295, #299 and #318 are merged. I haven't seen the 403 itself, since I can't read maybelle's logs.

**Change.** If the vault has `memory_lane_github_token`, it goes into memory-lane's env as `GITHUB_TOKEN`, which `settings.GITHUB_TOKEN` already reads. If not, nothing changes.

**Needs a person.** Create a fine-grained token, read-only, with access to public repositories, add it to the vault as `memory_lane_github_token`, then redeploy maybelle. I don't recommend reusing Jenkins' token: it likely has write scope, and memory-lane only reads.

Deploy: redeploy maybelle (after the vault has memory_lane_github_token)
Worked on by: magent, Justin, in #interfaces