Google docstring and AssertionErrors

[tazr]

I use asserts to check for post-conditions in my functions. I am also using Google docstrings to document those functions. Doing so, the ruff linter complains if I don't document the AssertionError in the docstring. However, the assert is not part of the API; it is a development tool that may be skipped during production. The Google Python Style Guide itself shows example of this here.
Is there a way to configure ruff to ignore AssertionError in Google docstring, or even actually flag the presence of AssertionErrors in the docstring? I am using DOC, and ignoring DOC501 would skip checks on all exceptions, which is not what I want.

[MichaReiser]

Can you tell me a bit more? I must be missing something important because I'm unable to reproduce this in our playground.

I understand that you use an assert and you have the DOC rules enabled. Did you configure the docstring convention to Google?

[tazr]

Sorry, I should have double-checked. The error was flagged by pydoclint, and not ruff.