Replies: 5 comments 2 replies
|
Good idea although how would the |
2 replies
|
I am currently considering the following commands, but would like opinions on what other options would be appropriate.
|
0 replies
|
Also, at what timing (trigger) should the following commands be executed to create a PR?
|
0 replies
|
Right now we just do |
0 replies
|
I don't want to focus on CI too much just yet until we get to the stable release. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
How about running the following cargo commands against all PRs, and if there are problems, they cannot be merged?
cargo buildcargo checkcargo testcargo benchcargo clippycargo fmtcargo fixAdditionally, I want to create pull requests for committing lock files and updating dependencies regularly in GitHub Actions workflow.
cargo doccargo generate-lockfilecargo updateI believe this would improve quality of the project, but would like to hear your thoughts on how far we should go with this.
All reactions