-
Notifications
You must be signed in to change notification settings - Fork 348
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
Allow empty commit message with a specified flag #2927
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.
Very nice! Really like the tests.
Left minor comments
@@ -425,6 +425,10 @@ components: | |||
type: object | |||
additionalProperties: | |||
type: string | |||
date: |
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.
[belong in another PR]
Commenting here as I couldn't find how to comment on file rename - why was nessie/files/ro_1k renamed to nessie/files/ro_1k.txt? |
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.
Nice!
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, after attending the rest of the reviewers question.
Added a
--allow-empty-message
flag that allows a commit to have an empty message, i.e.:lakectl commit lakefs://<repo>/<branch> -m "<whitespace character/s or nothing at all>" --allow-empty-message
will be allowed, yet
lakectl commit lakefs://<repo>/<branch> -m "<whitespace character/s or nothing at all>"
will not be allowed.
Closes #1395