From 4a5f0417c87de256ea30c54ef1cb58d12e3afa7d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?John=20Molakvo=C3=A6?= Date: Fri, 29 Aug 2025 13:31:26 +0200 Subject: [PATCH] feat(developer_manual): add new tags for issue classification MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: John Molakvoæ --- developer_manual/getting_started/coding_standards/index.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/developer_manual/getting_started/coding_standards/index.rst b/developer_manual/getting_started/coding_standards/index.rst index 8d232d177..45a0e3d56 100644 --- a/developer_manual/getting_started/coding_standards/index.rst +++ b/developer_manual/getting_started/coding_standards/index.rst @@ -41,12 +41,14 @@ The most important labels and their meaning: * ``4. to release`` - reviewed PR that awaits unfreeze of a branch to get merged or has pending CI jobs * ``needs info`` - this issue needs further information from the reporter, see :doc:`../../prologue/bugtracker/triaging`. This tag is typically combined with ``0. to triage`` to signal a bug report is not confirmed yet or a feature request has not been approved. + * ``needs review`` - this issue needs further investigation from the Nextcloud team, see :doc:`../../prologue/bugtracker/triaging`. * Tags showing the type of issue or PR * ``bug`` - this issue is a bug * ``enhancement`` - this issue is a feature request/idea for improvement of Nextcloud * ``technical debt`` - this issue or PR is about `technical debt `_ + * ``overview`` - this issue is a summary of a global effort, usually referencing other issues * Tags that classify an issue or PR