Ci/restore smoke ci 651#701
Merged
Merged
Conversation
|
@warisu Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
2 participants
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.
📝 Pull Request Summary
Description
This PR addresses Issue #651 by restoring the essential
smoke-civerification workflow framework. This pipeline was accidentally dropped in past repository housecleaning sweeps (chore(ci): delete smoke workflow/chore(ci): remove failing ci.yml). It re-establishes a deterministic quality baseline that must pass cleanly on all cross-branch merges.Key Modifications
.github/workflows/smoke-ci.ymllistening cleanly to any inbound pushes or incoming merge request modifications aimed at critical operational target branches (main,master,develop).cargo fmt --check: Restricts malformed text and spacing setups from leaking layout inconsistencies into code reviews.cargo clippy: Enforces idiomatic patterns and elevates standard lint warnings into strict build failures (-D warnings).cargo test: Automatically executes all test targets across workspace modules to maintain overall code health.Closes #651