Bug: the CI will fail currently since there are no tests

[guacs]

Description

pytest returns an exit code of 5 when it finds no tests. This causes the CI to fail. I think there are two options:

• disable the tests as part of the CI for this repo until tests are added
• use pytest_sessionfinish to change the exit code to 0 if the exit code is 5

URL to code causing the issue

No response

MCVE

# Your MCVE code here

Steps to reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots

No response

Logs

No response

Litestar Version

...

Platform

• Linux
• Mac
• Windows
• Other (Please specify in the description above)

[guacs]

@JacobCoffee can we update the issues templates to ask for the version of litestar-asyncpg along with the litestar version? I didn't see a ISSUES in the .github folder and I'm not sure how the templates are set up currently.

[JacobCoffee]

They are community health files that propagate to all repos here: https://github.com/litestar-org/.github

Maybe can change them there to just be "Package Version" instead?

[JacobCoffee]

Updated that to be Package Version instead

[guacs]

Updated that to be Package Version instead

I think it would be nice if we can ask for both the version of litestar as well as the package (if it's a litestar related plugin or something).