-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add GitHub Actions workflow ci.yaml #34
Conversation
Address compiler warnings given by `cargo check` or `cargo build`.
Address coding style issues given by `cargo fmt`.
Address issues given by linter, `cargo clippy`. * remove unnecessary return. * remove unnecessary to_string. * remove comparison of bool with true/false * remove unnecessary reference * remove redundant use tokio * remove unnecessary let binding * remove empty strings in println!() * use vec![] macro instead of pushing values to a mutable Vec * use &str instead of &String to avoid creating a new object
Add new GitHub Actions workflow `ci.yaml`, which runs `cargo fmt`, `cargo build`, `cargo test`, and `cargo clippy`.
4520480
to
91158c1
Compare
@@ -1,5 +1,7 @@ | |||
# Azure Provisioning Agent | |||
|
|||
[![Github CI](https://github.com/Azure/azure-provisioning-agent/actions/workflows/ci.yaml/badge.svg)](https://github.com/Azure/azure-provisioning-agent/actions) |
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.
Can you add some note to README to indicate that all PRs should run cargo fmt, cargo clippy, and cargo tests before submission, otherwise CI will fail and merging will be blocked.
Better yet, we can add some target to the Makefile such as "make tests", "make lint", "make format" to assist with invoking the proper cargo steps during development/submitting PR
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.
Added notes to CONTRIBUTING.md
.
Added makefile targets.
Ping, is there anything to be done? Can we merge? |
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.
LGTM
Address compiler warnings given by
cargo check
orcargo build
.Address coding style issues given by
cargo fmt
.Address issues given by linter,
cargo clippy
.return
.to_string
.bool
withtrue
/false
.tokio
.let
binding.println!()
.vec![]
macro instead of pushing values to a mutableVec
.&str
instead of&String
to avoid creating a new object.Add new GitHub Actions workflow
ci.yaml
, which runscargo fmt
,cargo build
,cargo test
, andcargo clippy
.Add GitHub CI status banner in
README.md
.Testing done
cargo test
,cargo fmt
,cargo clippy
passed.