-
Notifications
You must be signed in to change notification settings - Fork 834
tests: improve various CLI test coverage #8262
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
base: main
Are you sure you want to change the base?
Conversation
65c9fca to
fa148cc
Compare
rayaq-siddiqui
left a comment
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.
Looks great to me! I tested the sign/sparse/util tests and test_install_man_pages test locally in the jj cli and the output matches the test. Just have a question about the --abort flag below.
rayaq-siddiqui
left a comment
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!
| // Unsign multiple commits, including a previously-unsigned revision | ||
| let output = work_dir.run_jj(["unsign", "-r", "..@"]); |
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.
nit: It's more interesting to see rebased descendants "keep"s signed state. For example, if the @ revision was signed, unsign -r ..@- will rewrite the @ revision, which will have to be re-signed.
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.
Done, what do you think?
fa148cc to
e46f915
Compare
More of the same, like #8165. Feedback welcome.
Checklist
If applicable:
CHANGELOG.mdREADME.md,docs/,demos/)cli/src/config-schema.json)