-
Notifications
You must be signed in to change notification settings - Fork 596
feat(bin/oli): support cp to dir #6140
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
Conversation
No cargo test in CI... |
I think we can drop obvious commnets |
0bfd6ca
to
d6843e7
Compare
d6843e7
to
fac962c
Compare
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.
Pull Request Overview
This PR enhances the CI workflow for the bin/oli directory to support the "cp to dir" feature, ensuring that code linting and tests are executed in the CI process.
- Renames the CI job from "check_clippy" to "check_clippy_and_test"
- Adds a caching step using the sccache-action to speed up build times
- Combines cargo clippy and test executions with sccache environment support
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.
Others LGTM
1c3c881
to
523b1a8
Compare
@asukaminato0721 Would you like to try the testing style with #6174? I'm fine to either merge that one before or after this PR |
523b1a8
to
2bcea19
Compare
aha, I know the reason now, I enable the cargo test in CI. |
I can't understand
|
seems that the size of folder diffs. |
maybe we can ignore size of folder |
well...
|
another problem is that
this is not good, since the src and dst become the same. |
now pretty well. |
ping @xxchan |
Ideally we can have sth like |
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.
Thanks!
Thank you @asukaminato0721 for working on this and thank you @xxchan for the review! |
Which issue does this PR close?
Closes #2795.
part of #422.
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?