axodotdev / axodotdev/cargo-dist
Run `cargo-cyclonedx` from Rust (instead of only in the generated CI)
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 149
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 32
Description
Right now, `cargo-cyclonedx` is the _only_ external tool which is called by the generated CI workflow directly, instead of handled by `dist`.
It'd be useful to bring it in line with everything else and have `dist` run it directly, for consistency.
When this is resolved, it makes sense to add the `cargo-cyclonedx` check back to `do_env_test()`.
Contributor guide
Research direction
Start by tracing how dist handles external tools and how the generated CI workflow currently invokes cargo-cyclonedx. Then inspect do_env_test() and the existing checks around it. Done means dist runs cargo-cyclonedx directly for consistency with the other tools, and the cargo-cyclonedx check is restored to do_env_test().
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, release
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100