axodotdev / axodotdev/cargo-dist
Testing idea: repo with daily builds
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 149
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 32
Description
While we test cargo-dist's GitHub CI regularly in every PR, it would be nice to get a full runtest going on periodically. We could have a separate repository with a simple tool like a clone of axolotlsay, configured with a job to, once a day, pull in the latest cargo-dist, `cargo dist init`, and then kick off a tagged release. This could help us catch any possible CI issues early.
Contributor guide
Research direction
Start by reviewing the repository's existing GitHub CI and release workflows, then trace how `cargo dist init` and a tagged release are exercised today. Done means a separate repository contains a simple Rust tool, runs daily against the latest cargo-dist, initializes its configuration, and completes a tagged-release run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100