error message doesn't reveal problem, only solution

[ElsLommelen]

Here I describe an error that is unclear to me: it suggests to run devtools::document() and push an updated version of NAMESPACE, but running this command locally doesn't generate a new version of the NAMESPACE file. And the logging doesn't give the slightest hint on what has been tested, and what could be wrong there.

I like the fact that checklist errors always explain clearly what has to be done, and mostly this works fine. But in the few cases where it doesn't (often due to a different behaviour in different OS), I think it is a drawback that even in the logging it is unclear what causes the error. Would it be a possibility that for instance in this case, the differences between the NAMESPACE files, or even just both versions of the file, could be added to the logging? And more generally: could some more outputs be generated in the logging for the checklist specific tests?

[ThierryO]

Would adding a git diff to the error message a solution?

[ElsLommelen]

Yes, sounds like a perfect solution.