Publish testcraft from PRs to relevant branches
Metadata
Current evaluation
Enhancement (triaged, by maintainer) to add CI that publishes the testcraft snap from PRs to `latest/edge/craft-application-<pr#>` and main to `latest/edge/craft-application-main`, plus a PR comment with install commands. Explicitly blocked on canonical/craft-actions#48, which is still open; no such workflow exists in the repo yet.
Suggested action: keep open
Reason: The issue is explicitly labelled 'Status: Triaged, Type: Enhancement' and authored by maintainer lengau, and the requirement is concrete (branch scheme `latest/edge/craft-application-<pr#>` / `...-main`, no release to public channels, PR comment with `snap install` and `snapcraft refresh --amend`). It is explicitly gated on upstream work: the body says "Once we have completed https://github.com/canonical/craft-actions/issues/48", and that issue's status is confirmed as open/triaged ('Publish snap' action). Repo inspection confirms nothing is implemented yet — no `craft-actions` references and no `snapcraft/upload` usage in craft-application, and `.github/workflows/qa.yaml` only runs lint/test while release-publish.yaml only handles PyPI. Actionability is capped because the described implementation depends on an action that does not yet exist in the other repo, so either that lands first or the upload logic must be inlined with store credentials/secrets setup.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
11
Complexity:
50
Confidence:
80
Actionability:
55
|
keep open | Enhancement (triaged, by maintainer) to add CI that publishes the testcraft snap from PRs to `latest/edge/craft-application-<pr#>` and main to `latest/edge/craft-application-main`, plus a PR comment with install commands. Explicitly blocked on canonical/craft-actions#48, which is still open; no such workflow exists in the repo yet. | |
| qwen/qwen3.6-35b-a3b |
Impact:
65
Quick Win:
27
Complexity:
45
Confidence:
80
Actionability:
75
|
keep open | Enhancement to publish testcraft snap from PRs to branch-specific channels, blocked on craft-actions#48 which is still open | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
22
Staleness:
60
Complexity:
45
Confidence:
78
Support Request:
0
|
keep open | CI enhancement to publish testcraft snap from PRs/main to dedicated latest/edge branches with install-command PR comments. Triaged by maintainer, blocked on canonical/craft-actions#48 (still open), no activity in 256 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
55
Complexity:
40
Confidence:
80
Support Request:
0
|
keep open | CI enhancement to publish testcraft snap from PRs and main to dedicated branches with install command comments. Triaged but inactive for 215 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
65
Complexity:
45
Confidence:
75
Support Request:
10
|
keep open | Enhancement to publish testcraft snap from PRs to specific branches using a new action, improving reviewer testing. Currently triaged but inactive for ~6.7 months with only bot comments. |
Update history
No update history recorded yet.
Related work
-
Blocked By:
canonical/craft-actions#48
(confidence 92%)
Issue body states 'Once we have completed canonical/craft-actions#48'; that issue ('"Publish snap" action', GitHub Action equivalent of `snapcraft upload --release`) is still open and triaged.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #389 Update snapcraft test to stable in CI tests | fetch-service | open | CI spread tests still install snapcraft from latest/edge; maintainer wants the stable channel used in tests once craft-test is published there. Still open, unlabelled, no discussion. |