Issue & PR triage
Loading...
Showing 8 of 8 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
craft-actions issue #48 |
"Publish snap" action | lengau | 315d | keep open | 55 | 68 | 16 | Maintainer-filed, triaged enhancement asking for a `snapcraft/publish` action wrapping `snapcraft upload --release`, working with `snapcraft/pack`; still unimplemented, with a follow-up request for retry on store connection errors. |
|
craft-actions issue #5 |
[Feature Request] Publish rock to Github's Container Registry | gruyaume | 1363d | keep open | 50 | 75 | 22 | Feature request for a new `rockcraft-publish-ghcr` action to push built rocks to ghcr.io; acknowledged by maintainer in 2023 but ownership deferred pending `rockcraft upload`; still unimplemented. |
|
craft-actions issue #54 |
"snapcraft/test" action | lengau | 245d | keep open | 48 | 75 | 20 | Maintainer-filed, triaged enhancement: add a snapcraft/test action mirroring snapcraft/pack's inputs/outputs, plus an extra-params input and residual-artifact outputs. Not implemented (no snapcraft/test dir); pack only has a boolean 'test' input. |
|
craft-actions issue #37 |
[Feature request] Support proper caching when packing multi-architecture... | chanchiwai-ray | 601d | needs triage | 45 | 60 | 20 | Feature request to make the pack action's cache key architecture-aware so multi-arch matrix charm builds don't collide/override each other's cache. No maintainer response, no labels, still open. |
|
craft-actions issue #99 |
Pack actions need integration tests for the "test" boolean flag. | bepri | 64d | keep open | 40 | 82 | 17 | Pack actions expose a test flag, but integration coverage does not verify that enabling it successfully runs the corresponding test command; this triaged coverage gap remains open. |
|
craft-actions issue #20 |
[Feature Request] Add `name`, `version`, `arch` and any other useful... | ca-scribner | 1058d | needs triage | 40 | 45 | 10 | Feature request (open, no labels, no comments since ~1030 days) to expose name, version, arch and other rock metadata as outputs of the rockcraft-pack action, alongside the existing rocks output, to ease CI chaining with skopeo copy. |
|
craft-actions issue #47 |
Docs: link to examples in each action's README | jahn-junior | 322d | keep open | 30 | 65 | 15 | Docs request by a maintainer to add real-world usage examples to each action's README (like setup-uv), also to help users choose between setup and pack actions; still open, no discussion. |
|
craft-actions pr #136 |
docs: consistentize the READMEs | copilot-swe-agent | 7d | needs review | 30 | 60 | 15 | Documentation PR making README files across craft-actions consistent. Under review with 5 unresolved comments, CI passing. |