fiftyone-pr-triagelisted

# FiftyOne Issue Triage ## Triage Categories | Category | When to Use | |----------|-------------| | **Already Fixed** | Issue resolved in recent commits/releases | | **Won't Fix** | By design, out of scope, or not aligned with project goals | | **Not Reproducible** | Cannot reproduce with provided info | | **No Longer Relevant** | Outdated FiftyOne version, deprecated feature, or stale | | **Still Valid** | Confirmed bug or valid feature request | ## Triage Workflow ### Step 1: Read Issue Details Extract key information: ``` - Issue type: [BUG] / [FR] / [?] - FiftyOne version reported - Code to reproduce - Error message/traceback - Related module/feature ``` ### Step 2: Search Codebase ```bash # Search for related code grep -r "keyword" fiftyone/ grep -r "ClassName" fiftyone/core/ # Find the module mentioned in issue find fiftyone/ -name "*.py" | xargs grep -l "function_name" ``` ### Step 3: Check Git History ```bash # Recent commits related to issue git log --oneline --since="2024-01-01" -- fiftyone/path/to/module.py # Search commit messages git log --oneline --grep="keyword" # Check if specific function was modified git log -p --all -S "function_name" -- "*.py" # Blame specific lines git blame fiftyone/path/to/file.py -L 100,120 ``` ### Step 4: Check Related PRs/Issues ```bash # Search closed issues gh issue list --repo voxel51/fiftyone --state closed --search "keyword" # Search PRs gh pr list --repo voxel51/fiftyone --state merged --search "keyword" ``` #