rooster

Record Merged Issue Fix

The fix is merged to main, but not yet proven on staging.

Recorded the moment the merge succeeds, because the merge is the point of no return: from there the change is on main whatever happens next. ISS-24 merged and deployed, then a later step failed, and with nothing remembering the merge the loop rebuilt an already-merged fix twice.

Deliberately no status change -- fix_staged still means one thing only: somebody has confirmed staging is serving this commit.

post/api/rooster/issues/{issue_id}/merged

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/rooster/issues/{issue_id}/merged
  • Auth: none declared

Path parameters

issue_idstring uuid required

Request body

pr_urlstring required
branchstring required
summarystring required
how_to_checkstring
outcomestring
still_offstring
upstream_answerstring

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.