Inspect the inputs behind an environment assessment
Open a review run, choose the assessment for the environment in question, and scroll to Configuration and preferences. Its records describe that assessment’s instructions and code inputs. Use them when current settings or a newer repository revision tell a different story.
Find the settings that governed a run#
- Find out whether a review used its repository configuration
- Find who approved a preference used in an assessment
- Find a claim that a review preference withheld
- Check which review rules applied to one changed file
Trace repository guidelines into the assessment#
- Check whether guideline reads were enabled for a particular review
- Determine which version of an edited guideline governed a pull request
- Check how much of a guideline reached the assessment prompt
- Find out why an expected guideline is missing from the file list
- Correct a guideline the reviewer could not read as a file
- Repair a guideline that applies only on request
- Find a heading or section limit that cut off repository guidance
Check which related code reached the prompt#
- Check which ranked code locations reached an assessment
- Find out why related-code search could not select any input
- Check whether protected content prevented related-code selection
- Check whether a paid related-code search contributed to the review
Check related repositories at their running revisions#
- Check which companion repositories were read at their running revision
- Find why a companion has no recorded running revision
- Check which repository connection prevented a companion read
- Find why infrastructure evidence could not supply a companion revision
- Explain a companion count when some repository names are hidden