fix: use new workaround for using other actions
Metadata
Current evaluation
Merged fix for #71 replacing a broken composite action workaround with a new method copying files to unique paths. Applied the same update to charmcraft actions per reviewer feedback. Approved and integrated.
Suggested action: —
No scores available.
Issue body
This replaces the existing workaround which did not work with composite actions with a new one based on the workaround added to Testflinger in https://github.com/canonical/testflinger/pull/1014.
Copy to unique paths rather than to allow subsequent actions to also copy other files as needed.
Fixes #71
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged fix for #71 replacing a broken composite action workaround with a new method copying files to unique paths. Applied the same update to charmcraft actions per reviewer feedback. Approved and integrated. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
5
Complexity:
25
Confidence:
85
|
needs review | Updates snapcraft workflow to use a new composite action workaround based on Testflinger PR #1014. Copies files to unique paths to support subsequent actions. Fixes #71. Currently unreviewed and fresh. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1114 config: support use actions in charmcraft.yaml | charmcraft | merged | Merged update allowing actions in charmcraft.yaml instead of separate actions.yaml. Includes refactoring to fix circular imports. Approved by one reviewer across 10 files with 345 additions and 3 deletions. | |
| #142 fix the action generated by 'charmcraft init' | charmcraft | merged | Merged a fix for the action generated by charmcraft init, resolving issue #141. Approved by three reviewers and verified by the reporter. Corrects a generation bug in the init command. |