Rule-based fix: the finding was raised on a pull request
type | https://docs.frem.sh/reference/api/errors/rule-fix-pr-finding |
| HTTP status | 422 Unprocessable Content |
What it means
Returned by POST /orgs/{org}/code-security/secrets/findings/{id}/fix and POST /orgs/{org}/code-security/iac/findings/{id}/fix (rule-based fixes). No fix was requested and no pull request was opened.
The secret was found by the pull request gate, so it exists only on that pull request’s branch. A fix is proposed only for a finding on a branch that has been pushed.
Example detail message returned with this error:
- The finding was raised on a pull request. Fix it in the pull request itself.
The response also carries "reason": "pr_finding".
What to do
Fix the credential in the pull request itself, then rotate it.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/rule-fix-pr-finding",
"title": "Unprocessable Content",
"status": 422,
"detail": "...",
"reason": "pr_finding"
}Branch on type, not on title or detail - those are human-readable and may be reworded.