Files the issue when it's your bug.
When the cause is in your code, Repile opens a GitHub issue with the steps to reproduce, the evidence and the failing line, and links it back to the ticket.
Fatal error on PHP 8.3 in Form_Validator::sanitize() #422
- Reproduced on PHP 8.3.4, WP 6.6.2
- Deprecated dynamic property at includes/class-validator.php:88
- Passes on PHP 8.2; fix suggested in the issue
Every section of the issue is something Repile already did on the ticket.
Support tickets rarely include what a developer needs. These issues start with a reproduction and the exact line.
No noise in your issue tracker.
An issue only opens when the verdict is your bug. Everything else is explained in the ticket's internal note.
GitHub issue #422 opened
Steps, evidence and the failing line. Linked to ticket #418.
No issue
The note names the theme file and line. The draft has the workaround.
No issue
The note says what to ask their host, like raising the PHP memory limit.
Common questions.
Anything else? Write to [email protected] and a human answers.
Does it open pull requests?
When it's your bug, Repile opens the GitHub issue or PR.
What's in the issue?
The steps to reproduce, the evidence and the failing line, linked back to the ticket.
What if it's not our bug?
Then there is no issue. Repile explains the cause in the internal note, for example a theme conflict.