Add GitHub workflow that builds and tests the fetch-operator charm
Metadata
Current evaluation
Feature request to add GitHub workflow for building and testing the fetch-operator charm using charmcraft test. Issue is 715 days old with no maintainer engagement or labels.
Suggested action: close stale
Reason: The issue is 715 days old with no maintainer labels, no assignee, and only an auto-generated Jira sync comment. The requested work (adding CI workflow to the fetch-operator repository) appears to have never been completed, and there is no evidence of maintainer engagement or relevance to the current project state after over a year of inactivity.
Impact:
40
Quick Win:
28.0
Staleness:
85
Complexity:
30
Confidence:
65
Support Request:
20
Issue body
### What needs to get done
Add a GitHub workflow that builds [fetch-operator](https://github.com/canonical/fetch-operator) and tests it using `charmcraft test`.
The workflow should adjust the charmcraft.yaml file to use the specific commit we're building from
### Why it needs to get done
The fetch operator is one of the two biggest use cases of the fetch service.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
28.0
Staleness:
85
Complexity:
30
Confidence:
65
Support Request:
20
|
close stale | Feature request to add GitHub workflow for building and testing the fetch-operator charm using charmcraft test. Issue is 715 days old with no maintainer engagement or labels. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #203 Add fetch-operator charmcraft tests | fetch-service | closed | Closed and abandoned. The charmcraft test addition for fetch-operator was not implemented, with tracking superseded by internal Jira ticket CRAFT-3304. |