Skip to content

feat(developer_manual): add new tags for issue classification #13565

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
skjnldsv merged 1 commit into from
Aug 29, 2025
Merged

feat(developer_manual): add new tags for issue classification #13565

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions developer_manual/getting_started/coding_standards/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <https://en.wikipedia.org/wiki/Technical_debt>`_
* ``overview`` - this issue is a summary of a global effort, usually referencing other issues

* Tags that classify an issue or PR

Expand Down