-
Notifications
You must be signed in to change notification settings - Fork 201
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
fix: support prepared commit message #122
Conversation
When used as a git hook, using git commit -m'my message' was not making use of 'my message'. Now it does.
@leonardoanalista Build is passing on my fork Thank you |
it look like Travis it stuck.. I'l have a loo today ok? |
@Incorrupt release! |
Cool thank you! |
* 'master' of github.com:leoforfree/cz-customizable: fix: package url inside package.json after org creation (leoforfree#130) fix: update lodash security version feat: standalone version as global bin (leoforfree#129) build(deps): bump js-yaml from 3.12.2 to 3.13.1 (leoforfree#92) fix: support prepared commit message (leoforfree#122) build(deps): bump handlebars from 4.1.2 to 4.5.3 (leoforfree#110) docs: mention possible alternative path for config (leoforfree#123) subjectLimit option usage and validation (leoforfree#114)
This is not a fix, it looks more like a new feature to me. And it breaks the habit to just press The parsing of the commit message body does not take into account the format of the commit message, the same commit message that has been generated by this tool on the previous commit. It includes into the suggested commit body the line |
…ggest, interrupting the flow With the introduction of http://leoforfree/cz-customizable#122, cz-customizable pre-populates the subject and the body of the commit message with whatever values the _previous_ commit message had. When a commit message is long, this interrupts the developer workflow as a lengthy, non-editable string of text derived from the previous commit takes up all the space for the _current_ commit and confuses Inquirer CLI, which starts to render the cursor in an invalid location Related tickets: re leoforfree/cz-customizable#196, re leoforfree/cz-customizable#196
…ggest, interrupting the flow With the introduction of leoforfree/cz-customizable#122, cz-customizable pre-populates the subject and the body of the commit message with whatever values the _previous_ commit message had. When a commit message is long, this interrupts the developer workflow as a lengthy, non-editable string of text derived from the previous commit takes up all the space for the _current_ commit and confuses Inquirer CLI, which starts to render the cursor in an invalid location Related tickets: re leoforfree/cz-customizable#173, re leoforfree/cz-customizable#196
…ggest, interrupting the flow With the introduction of leoforfree/cz-customizable#122, cz-customizable pre-populates the subject and the body of the commit message with whatever values the _previous_ commit message had. When a commit message is long, this interrupts the developer workflow as a lengthy, non-editable string of text derived from the previous commit takes up all the space for the _current_ commit and confuses Inquirer CLI, which starts to render the cursor in an invalid location Related tickets: re leoforfree/cz-customizable#173, re leoforfree/cz-customizable#196
There are two kind of people:
git commit
git commit -m
cz-customizable is for those who
git commit
With this PR, cz-customizable is now for everybody!
When used as a git hook, using
git commit -m'my message'
was not making use of'my message'
. Now it does.This PR adds support for
subject
questionsubject
question and the other lines are passed as the default answer for thebody
questionIt is non invasive as it is passed as a
default
to enquirer. So the user can just press enter to use it or type another message if he wishes to.