Cryptograss:Moods/magenta-interface/todo: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
m Merged, says GitHub: https://github.com/cryptograss/memory-lane/pull/142 |
m Merged, says GitHub: https://github.com/cryptograss/maybelle-config/pull/174 |
||
| Line 12: | Line 12: | ||
link: https://github.com/cryptograss/maybelle-config/pull/174 | link: https://github.com/cryptograss/maybelle-config/pull/174 | ||
note: "Both have moved, so it's ready." | note: "Both have moved, so it's ready." | ||
done: true | |||
- task: "Redeploy maybelle and hunter, once #142 and maybelle-config#174 are in" | - task: "Redeploy maybelle and hunter, once #142 and maybelle-config#174 are in" | ||
who: justin | who: justin | ||
Revision as of 18:30, 9 October 2026
What the people in #magenta-interface have to do. magenta shows this list beside the Mood (memory-lane services/todo.py). Edit the YAML below: - task: ..., with who, kind, link, note and done as useful. Agents add what they leave someone to do, and mark what's done. Put a task in quotes if it has ": " or " #" in it (YAML reads those as a key and a comment); `backticks` make code.
- ☐Redeploy maybelle and hunter, once #142 and maybelle-config#174 are in
- ☐Try read-all in the car, after the voice PRs are deployedThe real test of ▶'s first sound, memos sent at stop, "Magent is thinking", and now "Pound general" and redeploys said.
Done (48)
- ☑
- ☑Merge maybelle-config#174 (clone memory-lane and magenta from cryptograss)Both have moved, so it's ready.
- ☑Transfer jMyles/memory-lane to cryptograss (Settings → Danger Zone → Transfer)18:27Z. magent-cryptograss kept write access; the org's hook hears it (an edit to #142 arrived at 18:28Z).
- ☑Let magent-cryptograss create repositories in cryptograss, and say go: magent transfers magent-cryptograss/magentaInvited; magent joined and moved magenta at 18:28Z. The old URL redirects, so every container's clone keeps working.
- ☑
- ☑Redeploy maybelle, once #141 is in
- ☑Look at the webhook's Recent Deliveries on GitHub: its URL, and what they answeredFound 18:19Z: the hook is the cryptograss org's (a star there reached magenta, signed and accepted), and memory-lane and magenta weren't the org's repositories. Hence the move.
- ☑Merge memory-lane#140 (the bot's ticks for a page go in one edit, and it checks they stayed)Three ticks in one second lost #139's; this is why.
- ☑Redeploy maybelle, once #140 is in
- ☑Merge memory-lane#139 (→ PickiPedia in the lightbox too)Merges cleanly with #138.
- ☑
- ☑
- ☑
- ☑Redeploy maybelle, once #138, #139 and maybelle-config#173 are in
- ☑Redeploy maybelle, for #135 to #137
- ☑
- ☑
- ☑
- ☑Look at your devices → everyone: was Sky's 12:54 device signed out, and when?Answered 10:26Z: none of Sky's were signed out, so that browser lost its sign-in (or it was the other one: home-screen app vs browser).
- ☑
- ☑Deploy PickiPedia again, once #172 is in (for pickipedia#136: code and anchors on the wiki's list)
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑Make the webhook secret (
openssl rand -hex 32); vault it asmemory_lane_github_webhook_secret - ☑Redeploy maybelle, once #131, #132 and maybelle-config#171 are in
- ☑Add the webhook on GitHub: pull requests, to
https://magenta.cryptograss.live/api/github/hook/ - ☑Deploy PickiPedia, for the todo tag (pickipedia#134)
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑Make the recovery key pair; keep the private half offline; public half in the vault
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑
- ☑Propose and approve the "magenta uploads" OAuth 2 app; put its keys in the vault
- ☑Tick High-volume (bot) access on the DrivingThatTrain@deploy-logs bot password
- ☑Redeploy maybelle, once the merges are in18:07Z, by JMyles (Cryptograss:Maybelle/deploy logs/26149367).
- ☑Redeploy hunter (the poller's greeting wording, #105; the to-do line in every wake, #117; handoffs in wakes, #118)