feat: manage Rust quality policy through repository#46
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a repository-managed Rust quality policy that can be shared across projects while still allowing project-specific extensions.
Changes
datarose.toml.verzly repository.[workspace.lints.rust]and[workspace.lints.clippy]policy for Rust workspaces.[lints] workspace = trueto workspace member crates..clippy.tomlas the shared Clippy threshold/config file..clippy.tomlfocused on Clippy configuration values instead of lint policy.quality.rustschema surface inrepository check.repository checkdetect missing Rust lint defaults and missing.clippy.toml.Notes
The default policy is intentionally portable: it forbids unsafe code, denies unused
must_useresults, denies the standard Clippy lint set, and blocks obvious development leftovers such asdbg!,todo!, andunimplemented!.Projects can extend or override the policy through
datarose.toml, then apply it withverzly repository update.