Skip to content

Issue Labels

This page documents the GitHub Issue label taxonomy for Pathary.

📌 View actual labels with colors →

Label Requirements

Every issue MUST have: - Exactly one Type label - Exactly one Priority label - At least one Area label

Optional labels: - Status labels for workflow tracking

Label Groups

Type Labels

Choose exactly one:

Label Description
bug Something isn't working correctly
enhancement New feature or request
documentation Improvements or additions to documentation
security Security issues or implementations
performance Performance optimization issues
refactor Code quality improvements without new features
chore Maintenance tasks (dependencies, tooling, CI)

Priority Labels

Choose exactly one:

Label Description
priority-p0 Critical/Blocker - Must be fixed immediately
priority-p1 High priority - Should be addressed soon
priority-p2 Medium priority - Normal timeline
priority-p3 Low priority - Nice to have

Area Labels

Choose one or more:

Label Description
area-auth Authentication & user management
area-2fa Two-factor authentication
area-email Email functionality (SMTP, OAuth, notifications)
area-admin Admin panel & server management
area-ui User interface & frontend
area-movies Movie tracking & ratings
area-tmdb TMDB API integration
area-database Database schema & migrations
area-docker Docker & containerization
area-api API endpoints & integrations

Status Labels (Optional)

Label Description
status-triage Needs initial review and categorization
status-ready Ready for development
status-in-progress Currently being worked on
status-blocked Blocked by dependencies or external factors
status-needs-info Waiting for more information from reporter

Community & Generic Labels

Label Description
good first issue Good for newcomers
help wanted Extra attention is needed
duplicate This issue or pull request already exists
invalid This doesn't seem right
question Further information is requested
wontfix This will not be worked on

Triage Checklist

When creating or triaging an issue:

  1. Pick Type - What kind of issue? (bug, enhancement, security, etc.)
  2. Pick Priority - How urgent? (p0, p1, p2, p3)
  3. Pick Area(s) - Which part of codebase? (auth, ui, database, etc.)
  4. Add Status (optional) - Where in workflow? (triage, ready, in-progress, blocked)

Examples

Security Vulnerability

Issue: "XSS vulnerability in user profile form"

Labels: security priority-p0 area-ui area-auth status-triage

Feature Request

Issue: "Add email notifications for new ratings"

Labels: enhancement priority-p2 area-email area-movies status-triage

Performance Issue

Issue: "Movie list page loads slowly with 1000+ movies"

Labels: performance priority-p1 area-movies area-database status-ready

Documentation Update

Issue: "Add OAuth setup instructions to wiki"

Labels: documentation priority-p2 area-email status-triage

Questions?

If unsure which labels to apply, add status-triage and a maintainer will review during triage.