issues

Acknowledge Deployed

The reporter says "got it" once their fix is live in production.

Frederick, 2026-08-08: "once it's out in production, it should then follow up and let them know, and then acknowledge that it's in production." The DM and the Needs You card are raised automatically the moment a deploy takes the issue live (production_promotion.py); this is the reporter's other half. Not a transition_issue() call -- deployed is terminal, there is nothing left to move to, only an acknowledgement to record.

Also the reporter's "mark completed" for the two other terminal code-lane states with no build to deploy: fixed_upstream (Marc's own fix shipped in his repo) and answered (Rooster closed it with an explanation instead of building it) -- see service.acknowledge_deployment's own docstring for why the same fact and the same column cover all three.

post/api/issues/{issue_id}/acknowledge-deployed

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/issues/{issue_id}/acknowledge-deployed
  • Auth: none declared

Path parameters

issue_idstring uuid required

Response

Successful Response

object required

Changes

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