Skip to main content
Open Learn in Graphify Cloud to see how your team’s pull request feedback shapes advisory reviews. Learning records dismissed findings, suppressed patterns, and the feedback behind them.

​
Teach Graphify on a pull request

Give feedback in the pull request conversation using the exact finding name from the Graphify review:
Feedback comes from trusted members. Fork activity is excluded. Graphify can also use a flagged line being changed before merge as a weaker, passive signal.

​
Read the Learning dashboard

Muted findings, Muted patterns, and Feedback last 30d summarize the workspace. The detail panels explain those totals:
  • Learned dismissals identify individual findings. Inspect the repository, dismissal history, and any conflicting confirmation. Dismissals are weighted and decay over time.
  • Suppressions show muted rules and their path scope, with the actor and pull request that introduced them.
  • Feedback activity shows recent commands and the findings or categories they refer to.
These panels are read-only. Give feedback on the pull request rather than looking for a dashboard switch to restore or edit a suppression.

​
What learning changes

Learning adjusts what advisory review surfaces and what stays quiet. It does not change the formal verifier, proof verdicts, counterexamples, or witnesses. The Verifier adjustments counter remains zero by design. See formal verification to interpret proof and behavior-change results.

​
Missing feedback

If Action needed reports a pending GitHub Issues permission, an installation administrator must approve the requested permission before PR-conversation feedback can be processed. Learning data also depends on the feature being enabled for your workspace. An empty panel can simply mean no eligible feedback has been recorded yet.