pre-merge review

A signed-in writer accepts, rejects or waives one graded item of one pre-merge run with a reason. The GitHub check run is re-posted so the decision shows on the pull request.

One resolution per itemKey per run; a later decision replaces the earlier one on the run (both remain in analytics). When the PR receives a new head, resolutions carry to the new run only for items whose judgment is unchanged (same key, same status), and the carried copy names the run where the person decided (carriedFrom). The merge path copies the run that graded the merged head, with its resolutions, into the intent's verification_result.premerge and the implementation note. Resolutions are deliberate human judgment and count toward the loop metric; automatic runs do not.

post/api/v1/intents/{id}/premerge-reviews/{reviewId}/resolutions

Path parameters

idstring required

id path parameter.

reviewIdstring required

reviewId path parameter.

Request body

itemKeystring required

The item's key as returned by GET (verification:<checkId> or <category>:<item text>).

actionstring required

accept (the drift is real and will be fixed), reject (the grader is wrong), or waive (real, merging anyway).

reasonstring required

Why (max 4000 chars). Required for all three actions.

Response

Decision stored; returns the updated run

object required

Changes