-
Notifications
You must be signed in to change notification settings - Fork 0
Fix GitHub Actions pipeline failures across CI, docs, and release workflows #12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -114,7 +114,9 @@ jobs: | |
| uses: dtolnay/rust-toolchain@nightly | ||
|
|
||
| - name: Install minimal-versions | ||
| run: cargo install cargo-minimal-versions | ||
| run: | | ||
| cargo install cargo-minimal-versions | ||
| cargo install cargo-hack | ||
|
|
||
|
Comment on lines
116
to
120
|
||
| - name: Check minimal versions | ||
| run: cargo minimal-versions check | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,57 @@ | ||
| # Contributing to Rust Guardian | ||
|
|
||
| Thank you for your interest in contributing to Rust Guardian! | ||
|
|
||
| ## Getting Started | ||
|
|
||
| 1. Fork the repository | ||
| 2. Clone your fork: `git clone https://github.com/YOUR_USERNAME/rust-guardian.git` | ||
| 3. Create a new branch: `git checkout -b feature/your-feature-name` | ||
|
|
||
| ## Development Setup | ||
|
|
||
| ### Prerequisites | ||
|
|
||
| - Rust 1.70 or higher | ||
| - Cargo (comes with Rust) | ||
|
|
||
| ### Building | ||
|
|
||
| ```bash | ||
| cargo build | ||
| ``` | ||
|
|
||
| ### Running Tests | ||
|
|
||
| ```bash | ||
| cargo test | ||
| ``` | ||
|
|
||
| ### Running Locally | ||
|
|
||
| ```bash | ||
| cargo run -- check src/ | ||
| ``` | ||
|
|
||
| ## Code Quality | ||
|
|
||
| Before submitting a pull request, make sure your code: | ||
|
|
||
| 1. Passes all tests: `cargo test` | ||
| 2. Passes clippy checks: `cargo clippy --all-targets --all-features -- -D warnings` | ||
| 3. Is properly formatted: `cargo fmt --all -- --check` | ||
|
|
||
| ## Submitting Changes | ||
|
|
||
| 1. Commit your changes with clear, descriptive commit messages | ||
| 2. Push to your fork | ||
| 3. Create a pull request against the `main` branch | ||
| 4. Describe your changes in the PR description | ||
|
|
||
| ## Questions? | ||
|
|
||
| If you have questions, please open an issue on GitHub. | ||
|
|
||
| ## License | ||
|
|
||
| By contributing to Rust Guardian, you agree that your contributions will be licensed under the MIT License. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that
CONTRIBUTING.mdis added to the repo and linked from the README, ignoringCONTRIBUTING.mdhere defeats the purpose of the link check (a future broken/renamed file link would no longer be caught). Prefer removing this ignore entry and letting the checker validate the relative link.