← Back to issue list

Disambiguate artifacts type in case of multiple valid inspections

View original Github issue

Metadata

Project
fetch-service
Number
#304
Type
issue
State
open
Author
cmatsuoka
Labels
—
Created
Updated
Closed
—

Current evaluation

Design decision needed for artifact type selection when multiple inspectors approve an artifact. Open for 646 days with no labels, assignee, or maintainer triage.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and no maintainer engagement beyond the original author's comments. The last substantive activity was cmatsuoka referencing fetch-service#296 on 2025-01-20, over a year ago. While the issue describes a valid design gap (last approved inspector wins when multiple inspectors approve), it requires architectural decision-making that hasn't been initiated by maintainers.

Impact: 45 Quick Win: 20.25 Staleness: 75 Complexity: 55 Confidence: 65 Support Request: 15

Issue body

### What needs to get done Decide an implement a strategy to select the file type for an artifact approved by multiple inspectors, e.g. a file project containing both charmcraft.yaml and rockcraft.yaml. ### Why it needs to get done Currently a rule for this situation is not specified and the last approved inspector run wins.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b
Impact: 45
Quick Win: 20.25
Staleness: 75
Complexity: 55
Confidence: 65
Support Request: 15
needs triage Design decision needed for artifact type selection when multiple inspectors approve an artifact. Open for 646 days with no labels, assignee, or maintainer triage.

Update history

Date Change
created

Related work

  • Related To: fetch-service#296 (confidence 90%)

    Open issue with nearly identical scope: 'Unable to disambiguate CRAFT package type with multiple CRAFT YAMLs'. Referenced directly by the issue author in the last comment.

Related issues

No related issues found above the similarity threshold.