Find out why an expected guideline is missing from the file list
On the environment assessment, open Configuration and preferences → Guideline files. Review the notes above Files before concluding the repository lacked the expected path.
Check the listing and the file limit#
A cut-short merge-base listing means discovery may have missed paths. A separate note counts files found beyond the guideline file limit. Neither note identifies a specific missing file. Expand Files to see the paths the review actually recorded.
Verify that the path exists at the merge base. If it should be read explicitly on future reviews, use the repository’s Settings → Guidance → Additional paths, one per line. Configured paths are considered before automatically discovered ones.