-
Notifications
You must be signed in to change notification settings - Fork 835
add error for committing an empty file set without a message #8243
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
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.
The following commits do not follow our format for subject lines:
- 9f3916e: add error for committing an empty file set without a message
Commits should have a subject line following the format <topic>: <description>. Please review the commit guidelines for more information.
hit this a few times unintentionally doing AoC, where the warning shown is hidden by the new editor opening
9f3916e to
623e703
Compare
All commits are now correctly formatted. Thank you for your contribution!
|
related issue #4414 |
|
I think it's valid to create an empty revision with an empty description. It might be okay to show a warning or a hint, though. |
This still can be dome intentionally with As is, the existing warning gets printed then immediately hidden by the editor window. Isaac mentioned on discord that the editor returning a non-0 exist code would abort the operation, (and it exists on vim and helix with |
|
Since it's not wrong to create a commit with no description, |
|
what is the point of the commit command if there is no message, tho? then it is just note that this PR is only about the situation where an empty file set is provided (which already has a warning) and no message provided, which I think is more likely to be a mistake than not. |
|
Yes, it's just |
hit this a few times unintentionally doing AoC, where the warning shown is hidden by the new editor opening, doing something like
jj commit d5p1.I have not done items in the checklist below because I am not sure if this is even the best approach.
Edit: On a personal level I'd rather the file set become the message in this case but that's probably not something
jjwants to do.Checklist
If applicable:
CHANGELOG.mdREADME.md,docs/,demos/)cli/src/config-schema.json)