Hello guys!! We were discussing at <#CSYLDDZUY|kot...

# kotest

[LeoColman]

Hello guys!!
We were discussing at #kotest-contributors a possible new label scheme for the Kotest repository. We've came up with this list and would love to know your opinion 🧵!

• bug 🐛: Issues that report a problem or error in the code.
• enhancement ✨: Suggestions for adding new features or improving existing ones.
• documentation 📚: Matters related to creating or updating project documentation.
• good-first-issue 👶: Suitable for newcomers looking to contribute to the project.
• question ❓: Inquiries or clarifications needed about the project.
• pinned 📌: Issues of high importance or that need to remain visible.
• assertions 🔍: Related to the assertion mechanisms within the testing framework.
• framework 🏗️: Pertains to the core structure and components of the Kotest framework.
• maintenance 🛠️: This label is for issues and pull requests that involve routine updates, codebase cleanup, and other non-feature work to keep the project running smoothly.
• multiplatform 🌐: This label is designated for issues and pull requests that concern the Kotest framework's compatibility or functionality across different platforms and environments.

[sam]

What about a tag for JVM only or do we not need that ?

[Adam S]

Looks good! I have one question about the multiplatform tag.: Is it worth splitting it into each target? So there would be target:js, target:native, target:jvm, and whatever other targets Kotlin has in the future? There are already JS specific issues (e.g. the issues related to nested tests), and I think it would help being able to group them.

[LeoColman]

Do we like it as multiplatform-js multiplatform-jvm, etc?