Run the milestone finish catch-up and notices (GET) — cronmilestonefinishsweepget
GET
/cron/milestone-finish-sweep
const url = 'https://example.com/api/cron/milestone-finish-sweep';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/cron/milestone-finish-sweepEvery run re-runs the milestone auto-finish rule (a milestone whose last open ticket closed while a guard held it finishes here, HO-15440), tells the building chat about a finish the last ticket close made (HO-19063) and notices the building milestones stuck on unproven criteria (HO-20705). Sends nothing to GitHub. Scheduled by the milestone-finish-sweep stage of the embedding-drain schedule in .slipstream.json (every 10 minutes). ok is false only when the sweep itself threw. Protected by CRON_SECRET via the x-cron-secret header.
Responses
Section titled “ Responses ”Sweep result
Media type application/json
object
ok
required
boolean
autoFinish
object
finished
integer
failed
boolean
finishNotices
object
announced
integer
failed
integer
unprovenNotices
object
candidates
integer
announced
integer
failed
integer
error
string
Missing or invalid CRON_SECRET