Finds the cause in your code.
With the failure in hand, Repile reads your plugin's source to find the exact line, and tells you whether it's your bug or something on the customer's side.
Our bug. Updating to 3.4 left the sender setting empty, so line 41 skips every email without logging it. Fix: fall back to the admin email and log the failure.
From the whole codebase to one line, starting at the failure.
Dana's checkout bug, followed through Formwise 3.4.2 and the 31 plugins on her site.
Formwise 3.4.2, the Harbor theme and 31 plugins, checked out at the versions she runs.
The failure was a tap on Place order, so Repile starts at the button's handler and what sits on top of it.
harbor-child/header.css:118 puts the header on top of the button.
- 116.site-header--sticky {
- 117 position: fixed; bottom: 0;
- 118 z-index: 9999;
- 119}
Every ticket ends with one of three verdicts
Other tools read your docs. Repile reads your code.
Documentation goes out of date. Your codebase can't, because it's the thing actually running on the customer's site.
A help-center bot reads
- Source
- “Email settings” article
- Written for
- Formwise 2.9
- After a release
- Someone rewrites the article
- Answer
- “Check your sender email.”
Repile reads
- Source
- github.com/formwise/formwise
- Checked out
- v3.4.2, the version Dana runs
- After a release
- Nothing to do. It reads the new tag.
- Answer
- class-mailer.php:41, with the fix
Common questions.
Anything else? Write to [email protected] and a human answers.
Where does it read the code from?
From your GitHub code. Repile checks out the release the customer has installed.
What if it's not our bug?
Repile tells you whether it's your bug, their theme, or their hosting, with the file and line for every claim.
Do we need to write help articles for it?
No. Ship a release and Repile already knows it. No articles to rewrite, no bot to retrain.