Diagnose a generated file that still appears in a review
Open the reviewed pull request and confirm its merge base before editing the repository's generated-file patterns. A pattern added only in the pull request cannot exclude that pull request's own changes.
Match the path and the effective review scope#
Check whether the file path matches a linguist-generated pattern at the merge base. Inspect nested .gitattributes files for patterns that unset the attribute on this path. Then open the repository's Settings → Review scope and verify that Exclude files marked linguist-generated is active.
Use Preview recent pull requests to inspect the scope. Check Not reviewed on a finished review for the recorded exclusion. If Proofline could not read the attributes, the file stays included and the review names the failure. Environment checks have their own scope.