Skip to main content

publish_plan

differential_engine::forge

Function publish_plan 

Source 
pub fn publish_plan(
    doc: &PlanDocument,
    findings: &[Finding],
    threads: &[RemoteThread],
    line_rule: Option<u32>,
) -> PublishPlan
Expand description

Which open findings a publish may send, and which it must leave.

A finding already published is not a candidate. A reply needs its thread to still exist and nothing else. A new comment needs its lines inside the request’s diff: within REQUEST_CONTEXT of a hunk in its file on its side, both ends. The old path rides along for a renamed file, because GitLab positions a comment by both paths.