You and I have very different ideas of what makes a good commit message
> Updated Gemfile.lock and added new dependencies (coderay, concurrent-… …ruby, crass, date, pry, method_source, public_suffix, puma, nio4r) and updated existing dependencies (rack-test, regexp_parser, xpath, nokogiri, racc, pg). Also added new files for a user authentication feature.
Describe the "what" but not the "why". Even "user auth wip" would be helpful. It's like having autogenerated code comments like:
// initialize variable i for later use in a loop
int i = 3;
GPT sometimes 'sees' the bigger picture though, for example when I commit a new rails app, instead of listing the individual files, it instead generated: "Added all files for a new Rails application, including controllers, models, views, tests, and configuration files." It could have said "new rails app", but it wasn't too ineloquent.
Code doesn’t say why, who and especially why not. (It sometimes may say when, but the important when is always yesterday anyway.)