Skip to content

Commit de42c72

Browse files
mcanouilgithub-actions[bot]
authored andcommitted
chore: rm footnote (replaced with PR comment
(cherry picked from commit c40e07a)
1 parent 92f3028 commit de42c72

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

docs/triaging/index.qmd

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -65,13 +65,11 @@ All issues beyond the next Milestone will be triaged to the "Future" milestone,
6565

6666
#### Labels
6767

68-
- Use clear and consistent labels such as [`bug`](https://github.com/quarto-dev/quarto-cli/labels/bug), [`enhancement`](https://github.com/quarto-dev/quarto-cli/labels/enhancement), [`support`](https://github.com/quarto-dev/quarto-cli/labels/support)[^support-issues], [`maintenance`](https://github.com/quarto-dev/quarto-cli/labels/maintenance), and [`documentation`](https://github.com/quarto-dev/quarto-cli/labels/documentation) to define the nature of the issue.
68+
- Use clear and consistent labels such as [`bug`](https://github.com/quarto-dev/quarto-cli/labels/bug), [`enhancement`](https://github.com/quarto-dev/quarto-cli/labels/enhancement), [`support`](https://github.com/quarto-dev/quarto-cli/labels/support), [`maintenance`](https://github.com/quarto-dev/quarto-cli/labels/maintenance), and [`documentation`](https://github.com/quarto-dev/quarto-cli/labels/documentation) to define the nature of the issue.
6969
Issues are expected to have exactly one of these labels.
7070
- Assign additional [labels](https://github.com/quarto-dev/quarto-cli/labels/) to categorise issues based on their type such as `html`, `website`, `installers`, `crossref`, *etc.*
7171
- Create custom labels if necessary to better categorise issues.
7272

73-
[^support-issues]: Should [`support`](https://github.com/quarto-dev/quarto-cli/labels/support) labelled issues be converted to discussions? [*Convert to discussion*]{.badge .rounded-pill .text-bg-primary}
74-
7573
#### Prioritisation
7674

7775
- Assess the severity and impact of issues to determine priority, *e.g.*:

0 commit comments

Comments
 (0)