Replies: 5 comments 2 replies
-
Good idea although how would the |
Beta Was this translation helpful? Give feedback.
-
I am currently considering the following commands, but would like opinions on what other options would be appropriate.
|
Beta Was this translation helpful? Give feedback.
-
Also, at what timing (trigger) should the following commands be executed to create a PR?
|
Beta Was this translation helpful? Give feedback.
-
Right now we just do |
Beta Was this translation helpful? Give feedback.
-
I don't want to focus on CI too much just yet until we get to the stable release. |
Beta Was this translation helpful? Give feedback.
-
How about running the following cargo commands against all PRs, and if there are problems, they cannot be merged?
cargo build
cargo check
cargo test
cargo bench
cargo clippy
cargo fmt
cargo fix
Additionally, I want to create pull requests for committing lock files and updating dependencies regularly in GitHub Actions workflow.
cargo doc
cargo generate-lockfile
cargo update
I believe this would improve quality of the project, but would like to hear your thoughts on how far we should go with this.
Beta Was this translation helpful? Give feedback.
All reactions