-
Notifications
You must be signed in to change notification settings - Fork 396
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
Disabling BLT commit message #2582
Comments
Does https://github.com/acquia/blt/blob/9.x/config/build.yml#L96 |
I realize I might be in the minority here, but I'm wondering if it might make more sense to disable the commit messages by default and make it optional to turn them on. Feels a bit heavy handed to me to require a commit message. From my experience, this is a self policing issue in that really bad commit messages are pretty useless and should be encouraged against as a culture. I also feel like it might be added friction for new user adoption as it takes a bit of digging to find out how to disable this setting. |
@grasmash Yes, it does.
|
Well, that warning is puzzling. Can you share the output of |
super bizarre... when I first ran $
|
Interesting. |
For the time being, because I gotta move on with some other stuff, I'm just going to throw this in composer.json
|
* Connects to #2582: Disabling BLT commit message. * Update GitCommand.php
I'm not able to reproduce this issue, but I added some output to assist with debugging if we hit it later. For now, I'd suggest setting |
I have also run into this issue in a new project on BLT 9.0.5. Per the documentation, I added the following to
|
Ah, this is probably because the command names have changed. The docs need to be updated. |
Looking at
With the implication that I would not use |
That is the best way to disable the git hook. Though your initial attempt also should have worked with something like...
Obviously that's not preferable. |
I'd like to echo the earlier suggestion for disabling this setting by default. I'm currently trying out BLT for the first time for an upcoming project and this tripped me up for a while. It's not clear that a local environment setup would police the commit messages to begin with, and it feels very unlikely that any project's convention would be to prefix issues with I do think this feature is really handy to have available, to easily configure a standard commit message for teams. The way it's setup out of the box just makes it a very frustrating obstacle in getting setup. |
There's a little more detail here: Add this snippet right underneath git.remotes configurations in the blt/blt.yml file.
And then initiate the config change: |
Bringing back an old issue...
#2128
My system information:
Output of
blt doctor
:When I run this command:
I get the following output:
And I expected this to happen:
I expect the pre-commit requirement to be ignored.
Here is my
blt.yml
, including the disable-targets and git hooks > pre-commit configuration settings that worked prior to the update.The text was updated successfully, but these errors were encountered: