makspll / makspll/bevy_mod_scripting
Semver Checks + Changelog dry run actions in CI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 649
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
I don't want to keep having to wrestle release-plz commits onto main before seeing what they will do.
I'd like to have a dry run action for release-plz or at least git cliff that will allow developing that config before merging to main.
I would also like to run cargo-semver-checks on each PR, and fail the PR if it's conventional commit doesn't cover a breaking change, I want to have better breaking change hygiene, and automatically collect migration guides eventually
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing CI configuration and the release-plz or git cliff configuration. Check how cargo-semver-checks and conventional commits can run on each pull request, then define done as a dry-run release workflow plus checks that fail when a breaking change is not represented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, rust
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100