Find out why a confirmed problem started no automatic fix
Read the Automatic fix line beneath the confirmation. A fix rule can be enabled now and still have been inapplicable when Proofline recorded the confirmation.
Check the rule that covered the confirmation#
No pull request opened because: Proofline stopped, and the line gives the reason. Why no pull request opened lists each reason and who can remove it.
None started because: the problem was confirmed, but the rule started no fix. Select the link in the line to open Automatic fixes. The line gives one of these reasons:
- automatic fixes are off: an administrator turns them on.
- the fix rule covers a repository, and its environment when that differs: the confirmation used another repository or environment. Request the confirmation in the rule's repository, or have an administrator change the rule.
- covers investigation findings only: an administrator changes the rule to include Scan findings.
- was turned on after this confirmation: the rule starts fixes only from confirmations recorded after it was turned on or last saved.
Once the rule is on and covers the confirmation's environment and repository, request the confirmation again. It checks the problem again at the same commit, and a result of Confirmed starts a fix.
Once Proofline has written the fix, the line also links Validation and patch. That page shows each validation step with its command and result, so you can see which build or test step failed. When Proofline wrote no patch, the page says why instead of listing steps. It also shows the patch, why a held fix was held, and the draft pull request when one was opened. Only the fix rule opens these pull requests, so the page has no control to apply the fix.