Property:Deploy note
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
Text What a pull request needs deployed, from the Deploy line at the foot of its description. Set by Template:PR.[unverified]
P
redeploy hunter +
redeploy hunter +
redeploy hunter +
redeploy hunter +
redeploy hunter. +
redeploy maybelle first (the sink), then hunter. +
redeploy hunter (containers rewrite mcp.json at startup); can ride with magenta#360. +
redeploy maybelle (the backup script and the cron-health job). +
redeploy hunter (the round that failed: it also puts magenta #360, #364, #370 and maybelle-config #269/#270 live) +
redeploy hunter +
redeploy maybelle, after resizing the volume in Hetzner. +
a person adds `memory_lane_alarm_key` to the vault, then redeploy maybelle (memory-lane and Jenkins both read it), after magenta's endpoint is merged. +
redeploy hunter +
redeploy hunter (with #276, already merged, in the same pass) +
redeploy maybelle (the fix); hunter at its next deploy (cosmetic) +
redeploy maybelle, with magenta#426 merged first or alongside (githouse's image is rebuilt and its tests run in the build) +
redeploy maybelle (with or after magenta#428; until memory-lane has the mailbox, githouse logs once that it didn't answer and merges nothing by mail) +
redeploy maybelle, with magenta#433 +
redeploy delivery-kid +
redeploy hunter +