The action works pretty well already, but it is far from perfect.

Here's a list of features I'd like to have:

• at the moment, the CI will either open a new issue or update an issue that has the configured title and label. However, sometimes the issue stays open long enough that something else changes and we get a combined issue for all changes. Renaming the issue or removing the label allows working around that, but requires manual action. Instead, we might want to (optionally) open separate issues for each test file?
• in addition to tests, the CI might be able to collect DeprecationWarnings, PendingDeprecationWarnings, and FutureWarnings and present them in a separate section / issue? For that, pytest-reportlog would need to serialize warning events, though, and we might need to create a separate action, too.