Cryptograss:Moods/ramp/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
Magent (talk | contribs)
ramp todo, 5 Nov: checked against GitHub, #ops and #emergence; Workspace verified; #250 conflicts; the plan page; dashboard and watches added (via update-page on MediaWiki MCP Server)
Magent (talk | contribs)
ramp todo, 6 Nov: githouse on maybelle decided and reworked (#250); #408 instead of a token; the rest rechecked (via update-page on MediaWiki MCP Server)
Line 1: Line 1:
<todo>
<todo>
- task: "Merge maybelle-config#246 (read-only GitHub token for memory-lane), then redeploy maybelle"
- task: "Review the reworked maybelle-config#250 (githouse on maybelle, mirror on hunter; your ten points of 2 Nov folded in)"
  who: re
  kind: review
  link: https://github.com/cryptograss/maybelle-config/pull/250
  note: "Reworked 6 Nov (e37e549). Read hardest: the keys relay and pushers.json (your point 1), fetch-only for hunter's mirror key (2), the bind assertion (5), and the containers' core.sshCommand per clone."
- task: "Confirm jenkins_github_ssh_key can push to the org's repos (githouse forwards pushes to GitHub with it); then merge #250 and redeploy maybelle, then hunter"
  who: justin
  kind: merge
  link: https://github.com/cryptograss/maybelle-config/pull/250
  note: "After re's review. If the key is read-only, fetching works and forwarding fails into githouse.log; pushes then stay on maybelle until a key that can push replaces it."
- task: "Merge magenta#408 (PR cards look at GitHub hourly), then redeploy maybelle"
   who: justin
   who: justin
   kind: merge
   kind: merge
  link: https://github.com/cryptograss/magenta/pull/408
  note: "The likely cause of the 31 Oct starvation: the cards' ten-minute look spent about 45 of the 60 unsigned calls an hour. With this, #246 (a token of memory-lane's own) is optional; watches (below) take merge asks off GitHub's API altogether."
- task: "maybelle-config#246 (read-only GitHub token for memory-lane): merge or close"
  who: justin
  kind: decision
   link: https://github.com/cryptograss/maybelle-config/pull/246
   link: https://github.com/cryptograss/maybelle-config/pull/246
   note: "Still open, mergeable (5 Nov). The webhook keeps PR cards fresh without it (magenta/402's card updated within minutes of its merge), but the ten-minute poll, to-do ticks, merge asks and status share 60 unsigned calls an hour and ran out on 31 Oct."
   note: "Optional once #408 is in. Justin, 6 Nov: no appetite for another token. Close it unless the asks starve again."
- task: "Verify Cryptograss:Moods/ramp/Plan, the settled design in one place"
- task: "Verify Cryptograss:Moods/ramp/Plan, the settled design in one place"
   who: justin
   who: justin
   kind: verify
   kind: verify
   link: "https://pickipedia.xyz/wiki/Cryptograss:Moods/ramp/Plan"
   link: "https://pickipedia.xyz/wiki/Cryptograss:Moods/ramp/Plan"
   note: "Written by magent 5 Nov from the record. Read it as the plan; say what's wrong."
   note: "Justin, 6 Nov: 'the plan page looks great'. Still a proposal until verified."
- task: "Say go on githouse-on-maybelle, then magent reworks #250 (re's points 2, 4 and 5 as requirements)"
  who: justin
  kind: decision
  link: https://github.com/cryptograss/maybelle-config/pull/250
  note: "#250 as opened puts it on hunter, and since 5 Nov it conflicts with production in three files (the Mood containers folding into /moods). Don't merge it; the rework supersedes it. Plan, section 3."
- task: "Set each repo's GitHub default branch to the branch that deploys: production for maybelle-config, pickipedia, arthel; main for magenta. blue-railroad-import: pick one"
- task: "Set each repo's GitHub default branch to the branch that deploys: production for maybelle-config, pickipedia, arthel; main for magenta. blue-railroad-import: pick one"
   who: justin
   who: justin
   kind: infra
   kind: infra
   note: "5 Nov: all six still default to main (pickipedia-mcp master). Then delete magenta's production branch (a634f16, Nov 2025) and #376's per-repo check can go. Plan, section 5."
   note: "6 Nov: all six still default to main (pickipedia-mcp master). Then delete magenta's production branch (a634f16, Nov 2025) and #376's per-repo check can go. Plan, section 5."
- task: "Merge commits only (squash and rebase off), merge queue off, on every repo githouse copies"
- task: "Merge commits only (squash and rebase off), merge queue off, on every repo githouse copies"
   who: justin
   who: justin
   kind: infra
   kind: infra
   note: "5 Nov: squash and rebase still allowed on maybelle-config, pickipedia, arthel, magenta, blue-railroad-import, pickipedia-mcp. githouse's merged-name detection needs merge commits."
   note: "6 Nov: squash and rebase still allowed on all six. githouse's merged-name detection needs merge commits."
- task: "Rulesets on the branches that deploy (PR required, no force-push, no deletion; admins bypass)"
- task: "Rulesets on the branches that deploy (PR required, no force-push, no deletion; admins bypass)"
   who: justin
   who: justin
   kind: infra
   kind: infra
   note: "5 Nov: none on any of the six. magent then tries a push to production that must fail, and reports. Private repos can't take rulesets on the free plan; githouse's hook covers those."
   note: "6 Nov: none on any of the six. magent then tries a push to production that must fail, and reports. Private repos can't take rulesets on the free plan; githouse's hook covers those."
- task: "Review magenta#333 (repo:branch autocomplete); merge after githouse is live"
- task: "Review magenta#333 (repo:branch autocomplete, now reading /api/branches/ from maybelle's githouse copy); merge with or after #250"
   who: re
   who: re
   kind: review
   kind: review
   link: https://github.com/cryptograss/magenta/pull/333
   link: https://github.com/cryptograss/magenta/pull/333
   note: "Reviewed by re 1 Nov, mergeable. Its branches.json URL moves with githouse to maybelle (re's point 7); magent updates it in the rework."
   note: "Reviewed 1 Nov; changed 6 Nov: the list comes from memory-lane's /api/branches/ (views_settings.api_branches), not a Caddy host on hunter."
- task: "Build the ramp view on magenta: open PRs across our repos, last five merged, who and where, last two mentions, sorted by last push or last mention, temperature"
- task: "Build the ramp view on magenta: open PRs across our repos, last five merged, who and where, last two mentions, sorted by last push or last mention, temperature"
   who: magent
   who: magent
   kind: code
   kind: code
   note: "Justin's memo, 30 Oct; the records half (cards) is live. After #246, so the view isn't starved of GitHub calls. Plan, section 2."
   note: "Justin's memo, 30 Oct; the records half (cards) is live. Plan, section 2."
- task: "Watches: merge and deploy asks resolved by commit ancestry against githouse's copy; deploys stamp the commit they deployed"
- task: "Watches: merge and deploy asks resolved by commit ancestry against githouse's copy; deploys stamp the commit they deployed"
   who: magent
   who: magent
   kind: code
   kind: code
   note: "After githouse is live. Plan, section 4. Deploy stamping is the prerequisite nothing does yet."
   note: "After githouse is live. Plan, section 4. Deploy stamping is the prerequisite nothing does yet."
- task: "Decide how emergents do git: the patch route, own GitHub accounts, or githouse"
- task: "Deploys clone from githouse's copy on maybelle instead of GitHub (Jenkinsfiles, deploy scripts)"
   who: justin
   who: magent
   kind: decision
   kind: code
   note: "githouse (above) is magent's and re's answer; this closes when it's live and re pushes a branch."
   note: "re's point 9: its own PR, after githouse is live and has run a few days."
- task: "Jenkins audit, re's open items: a policy on silent skips (pickipedia node/lua checks), pickipedia's chain-data warning that deploys stale silently, NVM/pnpm fetched from the network in every pipeline"
- task: "Jenkins audit, re's open items: a policy on silent skips (pickipedia node/lua checks), pickipedia's chain-data warning that deploys stale silently, NVM/pnpm fetched from the network in every pipeline"
   who: re
   who: re

Revision as of 04:32, 6 November 2026

  • ☐
    Review the reworked maybelle-config#250 (githouse on maybelle, mirror on hunter; your ten points of 2 Nov folded in)
    review · re
    Reworked 6 Nov (e37e549). Read hardest: the keys relay and pushers.json (your point 1), fetch-only for hunter's mirror key (2), the bind assertion (5), and the containers' core.sshCommand per clone.
  • ☐
    Confirm jenkins_github_ssh_key can push to the org's repos (githouse forwards pushes to GitHub with it); then merge #250 and redeploy maybelle, then hunter
    merge · justin
    After re's review. If the key is read-only, fetching works and forwarding fails into githouse.log; pushes then stay on maybelle until a key that can push replaces it.
  • ☐
    Merge magenta#408 (PR cards look at GitHub hourly), then redeploy maybelle
    merge · justin
    The likely cause of the 31 Oct starvation: the cards' ten-minute look spent about 45 of the 60 unsigned calls an hour. With this, #246 (a token of memory-lane's own) is optional; watches (below) take merge asks off GitHub's API altogether.
  • ☐
    maybelle-config#246 (read-only GitHub token for memory-lane): merge or close
    decision · justin
    Optional once #408 is in. Justin, 6 Nov: no appetite for another token. Close it unless the asks starve again.
  • ☐
    Verify Cryptograss:Moods/ramp/Plan, the settled design in one place
    verify · justin
    Justin, 6 Nov: 'the plan page looks great'. Still a proposal until verified.
  • ☐
    Set each repo's GitHub default branch to the branch that deploys: production for maybelle-config, pickipedia, arthel; main for magenta. blue-railroad-import: pick one
    infra · justin
    6 Nov: all six still default to main (pickipedia-mcp master). Then delete magenta's production branch (a634f16, Nov 2025) and #376's per-repo check can go. Plan, section 5.
  • ☐
    Merge commits only (squash and rebase off), merge queue off, on every repo githouse copies
    infra · justin
    6 Nov: squash and rebase still allowed on all six. githouse's merged-name detection needs merge commits.
  • ☐
    Rulesets on the branches that deploy (PR required, no force-push, no deletion; admins bypass)
    infra · justin
    6 Nov: none on any of the six. magent then tries a push to production that must fail, and reports. Private repos can't take rulesets on the free plan; githouse's hook covers those.
  • ☐
    Review magenta#333 (repo:branch autocomplete, now reading /api/branches/ from maybelle's githouse copy); merge with or after #250
    review · re
    Reviewed 1 Nov; changed 6 Nov: the list comes from memory-lane's /api/branches/ (views_settings.api_branches), not a Caddy host on hunter.
  • ☐
    Build the ramp view on magenta: open PRs across our repos, last five merged, who and where, last two mentions, sorted by last push or last mention, temperature
    code · magent
    Justin's memo, 30 Oct; the records half (cards) is live. Plan, section 2.
  • ☐
    Watches: merge and deploy asks resolved by commit ancestry against githouse's copy; deploys stamp the commit they deployed
    code · magent
    After githouse is live. Plan, section 4. Deploy stamping is the prerequisite nothing does yet.
  • ☐
    Deploys clone from githouse's copy on maybelle instead of GitHub (Jenkinsfiles, deploy scripts)
    code · magent
    re's point 9: its own PR, after githouse is live and has run a few days.
  • ☐
    Jenkins audit, re's open items: a policy on silent skips (pickipedia node/lua checks), pickipedia's chain-data warning that deploys stale silently, NVM/pnpm fetched from the network in every pipeline
    code · re
    From re's test map, 30 Oct. The mtime guard (#244) and the alarms (#402, #275) are done.