Research a pull request and publish a candidate finding
Start with a question on the pull request, inspect what Proofline established at the recorded commit, then choose whether to publish a candidate on GitHub.
Read research and publish a candidate#
To start research, comment on the pull request: mention Proofline, then write research and the question to investigate. Proofline replies with the run's credit and time limits. To follow the run, mention Proofline in a new comment followed by status. A mention followed by stop stops the research run, and it also cancels a running review and pauses Proofline's automatic reviews of the pull request; a mention followed by resume restarts them. Stopping research requires repository write access. Research reads the pull request's pinned code and recorded environment evidence. It does not run code experiments.
Open the pull request's Research section to see what a run examined, what it found, and what remains unknown. Check the recorded commit before using the result. A research candidate does not change the deployment verdict. Select Stop research to stop a pending or running run; this requires repository write access.
An administrator sets Credits per research run and Minutes per research run under Limits in Settings → Review policy → Models.
To publish a candidate as a GitHub review comment:
- Select Publish candidate… beside the candidate.
- Read the confirmation.
- Select Publish to GitHub.
Publication requires current repository write access and an open pull request whose head still matches the researched commit. Proofline also refuses it once the candidate's evidence has expired, or when you lack access to another repository the research read. The request records your approval. Publication requested confirms that Proofline accepted the request; it does not confirm that GitHub has received the comment.