order alphabetically

Signed-off-by: Ludvig Liljenberg <[email protected]>

Author: ludfjig

docs/github-labels.md

@@ -2,10 +2,10 @@
 
 We use GitHub labels to categorize PRs. Before a PR can be merged, it must be assigned one of the following **kind/** labels:
 
-- **kind/enhancement** - For PRs that introduce new features or improve existing functionality. This label also applies to improvements in documentation, testing, and similar areas. Any changes must be backward-compatible.
 - **kind/bugfix** - For PRs that fix bugs.
-- **kind/refactor** - For PRs that restructure or remove code without adding new functionality. This label also applies to changes that affect user-facing APIs.
 - **kind/dependencies** - For PRs that update dependencies or related components.
+- **kind/enhancement** - For PRs that introduce new features or improve existing functionality. This label also applies to improvements in documentation, testing, and similar areas. Any changes must be backward-compatible.
+- **kind/refactor** - For PRs that restructure or remove code without adding new functionality. This label also applies to changes that affect user-facing APIs.
 
 ---
 
@@ -14,8 +14,8 @@ We use GitHub labels to categorize PRs. Before a PR can be merged, it must be as
 Issues are categorized using the following three **GitHub types** (not GitHub labels):
 
 - **bug** - Reports an unexpected problem or incorrect behavior.
-- **enhancement** - Suggests a new feature, improvement, or idea.
 - **design** - Relates to design considerations or decisions.
+- **enhancement** - Suggests a new feature, improvement, or idea.
 
 To track the lifecycle of issues, we also use GitHub labels:
 
@@ -29,25 +29,26 @@ To track the lifecycle of issues, we also use GitHub labels:
 
 The following labels should be applied to issues prior to closing, indicating the resolution status of the issue:
 
-- **lifecycle/fixed** - The issue has been resolved.
 - **lifecycle/duplicate** - The issue is a duplicate of another issue.
+- **lifecycle/fixed** - The issue has been resolved.
 - **lifecycle/not-a-bug** - The issue is not considered a bug, and no further action is needed.
 - **lifecycle/wont-fix** - The issue will not be fixed.
 
 In addition to lifecycle labels, we use the following labels to further categorize issues:
 
-- **question** - The issue is a question or request for information.
-- **help-wanted** - The issue is a request for help or assistance.
 - **good-first-issue** - The issue is suitable for new contributors or those looking for a simple task to start with.
+- **help-wanted** - The issue is a request for help or assistance.
+- **question** - The issue is a question or request for information.
 
 ---
 
 # **Issues & PRs**
 
 In addition to **kind/*** labels, we use optional **area/*** labels to specify the focus of a PR or issue. These labels are purely for categorization, and are not mandatory.
 
-- **area/documentation** - Related to documentation updates or improvements.
 - **area/API** - Related to the API or public interface.
+- **area/dependencies** - Concerns dependencies or related components. This label is different from **kind/dependencies**, which should only used for PRs.
+- **area/documentation** - Related to documentation updates or improvements.
 - **area/infrastructure** - Concerns infrastructure rather than core functionality.
 - **area/performance** - Addresses performance.
 - **area/security** - Involves security-related changes or fixes.