repos

Prose Status

Prose-job lifecycle for one snapshot -- never wiki availability.

snapshot pins the answer the same way the estimate and generate bodies do. Without it this endpoint would keep reporting the latest snapshot's job while the client polls a job it just started on a different one, which would make the targeting above pointless the moment progress is rendered.

get/repos/{repo_id}/prose/status

Path parameters

repo_idstring required

Query parameters

snapshotstring nullable

Response

Successful Response

prose_job_idstring nullable required
prose_statusstring nullable required
phasestring nullable
triggerstring nullable
wiki_availableboolean required
wiki_formatstring nullable required
eligible_totalinteger nullable
eligible_missing_proseinteger nullable
selected_countinteger nullable
selected_page_idsstring[] nullable
completed_countinteger nullable
failed_countinteger nullable
estimated_cost_centsinteger nullable
actual_cost_centsinteger nullable
errorstring nullable

Changes