Improve issue and pull request labeling

[shibayan]

Summary

• use Issue Types and the organization Priority field as the primary Issue classification
• reserve release category labels for pull requests
• add path-based documentation and area:* labeling with the official GitHub labeler action
• add breaking-change and maintenance release-note categories
• document the Issue and pull request classification policy

Why

Issue Types and Issue fields provide structured Issue metadata, while pull requests still need labels for release-note categorization. Separating those responsibilities avoids duplicate classification and keeps labels useful for automation.

Impact

New Issue forms apply status: needs-triage instead of pull-request release labels. DNS provider requests also receive area: dns-provider. Pull requests from branches in this repository receive additive path-based labels; manually assigned labels are not removed. Pull requests from forks are labeled manually so the workflow can use the safer pull_request event without granting write access to untrusted contributions.

Validation

• git diff --check
• verified the pinned actions/labeler commit corresponds to v6.2.0
• reviewed the labeler configuration against the repository paths
• restricted the write-enabled labeler job to same-repository pull requests

[Copilot]

Pull request overview

This pull request updates the repository’s issue/PR classification approach by shifting issues to structured metadata (Issue Types + org Priority field) while keeping labels focused on pull-request release-note categorization and automation.

Changes:

• Documents the intended issue and pull request classification policy in CONTRIBUTING.md.
• Adds a PR labeler workflow plus .github/labeler.yml rules to apply documentation/area:* labels based on changed paths.
• Updates issue forms to apply triage/area labels instead of PR release-category labels, and extends release-note categories for breaking-change and maintenance.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
CONTRIBUTING.md	Adds documented policy for issue types/priority fields and PR release-category labeling.
.github/workflows/pr-labeler.yml	Introduces a workflow to apply path-based labels to pull requests via actions/labeler.
.github/release.yml	Adds release-note categories for breaking changes and maintenance.
.github/labeler.yml	Defines path-to-label mappings for documentation and area:* labels.
.github/ISSUE_TEMPLATE/feature_request.yml	Switches feature requests to status: needs-triage instead of PR-style release labels.
.github/ISSUE_TEMPLATE/dns_provider_request.yml	Adds area: dns-provider + triage labeling for DNS provider requests.
.github/ISSUE_TEMPLATE/bug_report.yml	Switches bug reports to status: needs-triage instead of PR-style release labels.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.

Suppressed comments (1)

CONTRIBUTING.md:66

• The classification policy mixes “exactly one release category label” with applying breaking-change, and it also implies Dependabot labels are configured here. Since .github/release.yml treats breaking-change as its own release-notes category, it’s clearer to explicitly state that breaking-change is an additional (optional) label that can be combined with the single category label. Also, Dependabot adds the default dependencies (and ecosystem) labels automatically unless you override labels in dependabot.yml, so “through its repository configuration” is misleading.

Pull requests use exactly one release category label: